Guide contents

Pausing, disabling, uninstalling

Every level of "make it stop" Merget offers, from gentlest to nuclear. Pick the lightest one that does what you need. For what's stored where (and what deleting actually removes), see Sync & privacy.

Hold my edits: manual commit mode

If you just want control over when checkpoints happen, you don't need to disable anything. Turn on Commit manually in Settings: your hand-written edits are held until you press the Commit button in the repo toolbar, so one step can cover a whole sitting. Agent edits are still committed with their prompts regardless.

Pause committing for one repo

The Merget tray (menu bar) icon has a Repositories submenu with a checkmark per linked repo. Uncheck a repo to stop committing in it; check it again to resume. The rest of your repos are unaffected.

Turn off auto-track

The auto-track toggle in Settings controls whether Merget sets up committing automatically when a supported coding tool starts a session in a folder. Turn it off and Merget stops initializing committing in new folders. (Repos already set up keep committing — pause or unlink those separately.)

Quit the app

Closing the Merget window only hides it — the tray icon stays and committing daemons keep running. To actually stop committing on this machine, choose Quit Merget from the tray menu. Nothing commits again until you reopen the app.

Remove the agent plugins

To take Merget out of your coding agents entirely:

merget plugins remove                   # all agents
merget plugins remove --agent claude    # just one (claude, codex, cursor, copilot)

This removes the plugin packages, the merget skill, and the hook entries from each agent's configuration, so your agents stop reporting sessions. Reinstall any time with merget plugins install. See the CLI reference.

Do this before uninstalling the app, so agent configurations aren't left pointing at hooks that no longer exist. After that, remove the app the normal way for your operating system. Note that the merget CLI is part of the app — once the app is gone, merget commands stop working too (which is exactly why the plugins should be removed first, while the CLI still runs).

To stop Merget tracking a repo on this machine without touching its history: right-click the repo's card on the Dashboard and choose Unlink folder. The folder is disconnected from the app; your files and the cloud copy are untouched, and you can re-link later.

The repo settings dialog's Danger tab has a stronger unlink that also deletes the local .merget/ folder — local history is removed from the folder, but the server copy keeps everything that was synced.

Delete history

  • Local: deleting a repo's .merget/ folder removes all local history for that repo. Your working files are untouched. The registered server copy is not affected — everything already synced stays on Merget's servers until you delete the repo there.
  • Server: open the repo's settings dialog (from its Dashboard card menu), go to the Danger tab, and delete the repository. There's an option to delete the local folder at the same time.

Delete your account

The nuclear option lives in Settings, in the Danger zone: Delete account (you confirm by typing your username). It permanently removes your account and your personal repositories. What deletion covers — and what little remains — is spelled out in Sync & privacy.

Under the hood

These controls operate at different layers, which is why they compose. Manual commit mode and auto-track are written to Merget's machine-wide config, where the committing daemon picks them up without a restart. The per-repo tray toggle enables or disables that repo's daemon inside the app. merget plugins remove edits the agents' own config files (removing only Merget's hook entries — your other hooks are preserved) and deletes the plugin packages from your home directory. Unlink clears the app's folder association; the .merget/ folder is the repo's complete local object store, so deleting it is a true local wipe.


Next: Troubleshooting · Related: Settings · Sync & privacy