Uninstalling

Three levels, depending on how much you want gone.

	Removes	Keeps
Disconnect a client	Sigil’s entries in that agent’s config	Everything else
Wipe data	Facts, documents, the database	The install
Remove entirely	All of it	Your external Postgres database, if you had one

---

Disconnect agents

sigil uninstall [--dry-run]

Walks every detected AI client — Claude Code, Cursor, Codex CLI, Kiro — and lets you pick which to remove Sigil from. Each picked client gets:

• Its MCP entry removed (other entries in the file preserved)
• Its Sigil instructions / rules / steering file deleted
• Hook entries stripped (Claude Code only)

Your data is not touched. ~/.sigil/, the database, and every stored fact survive. Reconnect any time with sigil connect.

sigil uninstall --dry-run    # see exactly what would be removed

---

Wipe the data

sigil reset               # confirm, then drop the database and wipe everything
sigil reset --yes         # skip the prompt (scripting)
sigil reset --keep-db     # wipe config and disconnect agents, keep the data

Destructive. Export first:

sigil export --format=json --output=backup.json

---

Remove everything

1. Unwire the agents (so no config is left pointing at a binary that’s about to vanish):

   sigil uninstall

2. Remove the install, config, and embedded database:

   rm -rf ~/.sigil

3. Remove the PATH line the installer added to your shell rc (~/.zshrc, ~/.bashrc, or similar):

   export PATH="$HOME/.sigil/bin:$PATH"

4. Verify Claude Code is clean — sigil uninstall handles this, but if you skipped it:

   • Remove the four Sigil hook entries from ~/.claude/settings.json
   • Remove the @~/.sigil/CLAUDE.md line from ~/.claude/CLAUDE.md

5. Drop the database, if you used an external Postgres. Sigil doesn’t touch it:

   dropdb sigil
   dropuser sigil_app

   Or delete it from your managed provider’s console.

rm -rf ~/.sigil deletes embedded memory

In embedded mode your entire brain lives in ~/.sigil/db/. Deleting the directory deletes your memory. With an external Postgres, only configuration and runtime state are in ~/.sigil/ — the memory survives, and reinstalling and pointing at the same database gets it all back.

---

Client config paths

If you’re cleaning up by hand:

Client	File	What to remove
Claude Code	~/.claude/settings.json	Four Sigil hook entries
Claude Code	~/.claude/CLAUDE.md	The @~/.sigil/CLAUDE.md line
Cursor	~/.cursor/mcp.json	The sigil server entry
Codex CLI	~/.codex/config.toml	[mcp_servers.sigil]
Codex CLI	~/.codex/AGENTS.md	The Sigil steering block
Kiro	~/.kiro/settings/mcp.json	The sigil entry
Kiro	~/.kiro/steering/sigil.md	Delete the file
Continue	~/.continue/config.json	The sigil entry
Cline	cline_mcp_settings.json	The sigil entry
Windsurf	~/.codeium/windsurf/mcp_config.json	The sigil entry
Claude Desktop	claude_desktop_config.json	The sigil entry

---

Taking your memory with you

sigil export --format=json --output=sigil-brain.json      # structured
sigil export --format=markdown --output=sigil-brain.md    # readable
pg_dump "$YOUR_DATABASE_URL" > sigil.sql                  # complete

The JSON and Markdown exports are plain files with no Sigil-specific dependencies. Your memory isn’t locked in anything.

---

Reinstalling later

If you kept the database, reinstalling gets everything back:

curl -fsSL https://raw.githubusercontent.com/Anmol-Srv/sigil/master/install.sh | sh
sigil init --url "postgres://…"

Migrations find the schema current and your whole brain is there.