Install
CLI reference

Uninstall

Remove Blamely cleanly. Attribution history is kept by default — if you want a true wipe, the last step shows how.

Standard uninstall

terminal
blamely uninstall

This reverses everything blamely install did:

  • Removes the daemon agent (launchd / systemd / Scheduled Task).
  • Unsets git config --global core.hooksPath (restoring whatever was there before).
  • Removes Blamely’s entries from ~/.claude/settings.json, ~/.cursor/hooks.json, ~/.codex/config.toml, ~/.copilot/hooks/blamely.json, ~/.gemini/settings.json. Other entries are left intact.
  • Removes the PATH line from your shell rc file.
  • Removes the stable binary at ~/.blamely/bin/blamely.

What it keeps:

  • The SQLite database at ~/.blamely/db.sqlite (raw edit events).
  • Existing refs/notes/blamely notes on commits.

That way reinstalling later picks up where you left off.

Full wipe

To remove every trace, including history:

terminal
blamely uninstall
rm -rf ~/.blamely

On Windows:

terminal
blamely uninstall
rmdir /s /q %USERPROFILE%\.blamely

Existing git notes are unaffected by removing ~/.blamely — they live in your repo’s refs/notes/blamely ref. To remove notes from a specific repo:

terminal
git update-ref -d refs/notes/blamely

To remove notes from the remote (only relevant if you pushed them):

terminal
git push origin :refs/notes/blamely

Editor plugins

Uninstalling the CLI doesn’t remove the editor plugins. Remove them from each editor’s extension manager:

  • VS Code — Extensions → Blamely → Uninstall.
  • Cursor — same as VS Code.
  • JetBrains — Settings → Plugins → Installed → Blamely → Uninstall.

Plugins will keep running but won’t be able to talk to a daemon that isn’t there; they log a warning every 30 seconds and otherwise stay quiet.

Reinstall later

Just run blamely install again. If your ~/.blamely/db.sqlite is still there, every previous edit event is preserved. Git notes that exist on commits are read as-is — they were never deleted.

Next

Something unclear or wrong? Tell us.