# faq

Every question, answered.

git-to-x connects your GitHub repo and X account — every day it generates a designed commit card and posts it automatically. Here are the most common questions about how it works, what access it needs, and what it costs.

// posting

Will this spam my followers?

No. One post per day, only on days you actually commit code. Zero-commit days get zero posts — no filler, no empty cards, complete silence. Long streaks even earn a freeze: one missed day is forgiven when you've shipped 7+ days straight before it.

Can I review posts before they go out?

Yes. Every morning the draft lands in your Telegram (and on your dashboard) before it posts — tap to approve, reply to rewrite it, or do nothing and it posts itself on schedule. Manual mode is also available: you trigger each post yourself. Switch modes any time in Settings.

What happens on days I don't commit?

Nothing. No post, no notification, no embarrassing 'day off' card. Silence is the correct output for a zero-commit day.

What's in a post? Does it write captions with AI?

The stat card text is purely data-driven — commits, additions, deletions, streak. For the tweet caption, git-to-x drafts an ICP-aware caption via Telegram: you get the draft, approve or edit it, and it posts. Ignore it and the stat-based fallback caption posts automatically. No surprises.

Can I post to multiple platforms?

Yes. Pro posts to X, LinkedIn, and Bluesky automatically. Connect each in Settings — each is independent, so you can enable only the ones you want.

// security & access

What access does the GitHub App get?

Read-only: contents:read and metadata:read. We only ever request commit stats and commit messages — we never query file contents or diffs, even though the underlying permission would technically allow it. It cannot write code, open PRs, or create branches. GitHub itself blocks any write operation on our end.

Does git-to-x ever see my code?

No. We call GitHub's API for three numbers per commit window: additions, deletions, and the commit message. Diffs, file contents, blobs: never requested, never transferred, never stored.

How do I revoke access?

One click at github.com/settings/installations — no email needed, instant. For X/LinkedIn/Bluesky, revoke in each platform's connected apps settings, or disconnect from your git-to-x Settings page.

Is the codebase auditable?

The tools that run on YOUR machine — the g2x CLI and the MCP server — are published to npm (MIT licensed), so you can read exactly what leaves your terminal. The hosted service uses a read-only GitHub App permission enforced by GitHub itself, and we only ever query commit stats and messages — never file contents. Revoke access anytime from github.com/settings/installations.

// pricing & billing

What does 'locked forever' mean?

Beta Pro is $9/mo for as long as you subscribe — the price never increases for you, even after we raise it to $29. Cancel any time. If you re-subscribe after cancelling, you rejoin at the current public price.

What's included in the free plan?

10 auto-posts per month to X, 6 card designs rotating daily, and a 14-day full Pro trial on signup (all features, no card required).

Can I cancel any time?

Yes. No lock-in, no cancellation fee.

// cli & mcp

What is the CLI for?

Text posts from your terminal. Run 'g2x "shipped dark mode"' and it posts to X (and optionally LinkedIn/Bluesky) immediately. Your exact words, untouched. 50 posts/month on Pro.

What is the MCP server for?

Same as the CLI, but from inside Cursor, VS Code, or Claude Code via MCP. Say 'tweet this: shipped dark mode' in the AI chat panel and it posts without leaving your editor. Install with: claude mcp add git-to-x -- npx -y git-to-x-mcp

Still have a question? DM @manoj_surya_ on X →