FAQ
Short answers, each with a link to the page that covers it fully.
Does Merget replace Git? No — Merget is its own version control system, not a Git layer, and a Merget repo is not a Git repo. You can import existing Git history into Merget. See Merget and Git.
Where do my prompts and code go? To Merget's servers: your code syncs to your repo's remotes, and your prompts and diffs go to Merget's processing service as part of committing. The complete answer — including who can read what — is in Sync & privacy.
Can I use Merget offline? No. Sign-in is required before anything commits, and committing itself relies on Merget's processing service to organize work into goals, prompts, and steps. See How Merget works.
Which agents are supported? Claude Code, Codex, Cursor, and GitHub Copilot. Anything else still gets file-change committing, but without prompts or transcripts. See Supported agents.
Is Merget affiliated with Anthropic, OpenAI, Cursor, or GitHub? No. Their coding tools are independent products; Merget doesn't sell or distribute them and isn't associated, partnered, or endorsed by their makers. Merget runs the copy you installed — inside the app via a virtualized terminal — and commits its sessions through the tool's own hook mechanism. See Supported agents.
What's a "step"? One committed checkpoint: a snapshot of your files plus what changed and why. The CLI and the agent skill call the same object a "subprompt." See the glossary.
Can my agent run Merget itself? Yes — Merget installs a skill that teaches your agent to commit, read history, check out, and merge on request, so "commit this with a good message" works as a plain instruction. See Your agent and Merget.
How do I share a repo with someone? Add them as a collaborator (or put the repo in an organization). See Collaborators & sharing.
How do I stop committing? There's a whole ladder, from manual commit mode through pausing a repo to removing the plugins and deleting data. See Pausing, disabling, uninstalling.
Is my data used for training? Merget offers a per-repo opt-out covering Merget's own reuse of your committed data, but history processing runs on third-party AI providers and Merget does not attach "do not train" terms to those calls — so no provider-level guarantee exists, and we won't claim one. See Sync & privacy.
Next: Glossary · Related: Sync & privacy · Merget and Git
