Operate
Remove Fidacy
Leaving should be as verifiable as arriving. This page removes Fidacy from your agents and your machines, in the order that keeps your evidence intact.
1 · Export your evidence first
Receipts, decisions and anchored checkpoints are yours. Export them before you remove anything, because a signed receipt keeps its value to an auditor, an insurer or opposing counsel long after you stop using the product.
In the Console, open Control Room and export an Incident Pack for each decision you need to keep, or pull them over the API. Each pack carries the decision, the authority in force, the hash chain and the Merkle proof.
2 · Revoke authority
Revoking is how you take authority away from an agent. There is no separate unassign step: a revoked mandate stops every future action bound to it, while existing receipts stay verifiable.
In the Console, open Authority Builder and use Revoke on each mandate listed under Authority in force. Revoking is immediate and cannot be undone, so reissue rather than expect a restore.
3 · Revoke your API keys
Removing the local install does not invalidate a key. Any copy of a key that still exists, in a shell history, a CI secret or a teammate machine, keeps working until you revoke it. In the Console, open Settings and revoke every key, test and live.
4 · Stop local enforcement
If you ran npx -y @fidacy/mcp install --write or install-hooks, Fidacy registered an MCP server and two hooks on this machine. The hooks run on every tool call in every project, not only the ones using Fidacy, so removing them is what stops the gate.
| Host | File | Remove |
|---|---|---|
| Claude Code | ~/.claude.json | the fidacy entry under mcpServers |
| Claude Code | ~/.claude/settings.json | hook entries whose command mentions fidacy |
| Claude Desktop | ~/Library/Application Support/Claude/claude_desktop_config.json | the fidacy entry under mcpServers |
| Cursor | ~/.cursor/mcp.json | the fidacy entry under mcpServers |
| Windsurf | ~/.codeium/windsurf/mcp_config.json | the fidacy entry under mcpServers |
| Codex | ~/.codex/config.toml | the [mcp_servers.fidacy] block |
| Codex | ~/.codex/hooks.json | hook entries whose command mentions fidacy |
Each file the installer touched has a .fidacy-backup copy next to it, holding the configuration as it was before Fidacy was added.
5 · Delete the local credential and trail
The CLI stores your account key and a local audit trail under ~/.fidacy. Export anything you want to keep from ~/.fidacy/audit first, then remove the directory.
rm -rf ~/.fidacy
6 · Remove the packages
If you installed globally rather than running through npx, remove the package and the cached copy npx keeps.
npm ls -g --depth=0 | grep -i fidacy npm uninstall -g @fidacy/mcp
For an application dependency, remove the package from your package.json and delete the adapter code that calls it. Remember to fail closed where the gate used to be, or the action that Fidacy was stopping now runs unchecked.
What survives removal
- ·Signed receipts stay verifiable with the public key set, without an API key and without us.
- ·Anchored checkpoints remain on chain and are independent of your account.
- ·Exported Incident Packs stay verifiable offline.
- ·Your agents keep working. They simply act without a gate and without evidence.