Removing Cardinal from a computer
One line per computer undoes what the install line did. Use it when you leave a workspace, when a workspace's access has ended, or when you just want Cardinal off that computer. It needs Node.js 20 or later, which the install line needed too, and no key.
On a Mac or on Linux
In a terminal, with your own Cardinal address in place of the dots:
curl -fsSL .../leave.sh | CARDINAL_URL=... sh
On Windows
In PowerShell:
$env:CARDINAL_URL='...'; irm .../leave.ps1 | iex
What it does
- Takes Cardinal's entries out of your Claude settings file (
~/.claude/settings.json, or%USERPROFILE%\.claude\settings.jsonon Windows): the telemetry settings and the session-end hook that carry this computer's key. Everything else in the file stays, and it keeps a copy first, namedsettings.json.cardinal-removed-followed by the date and time. If the file has a JSON error it is left alone and the note says so. - Leaves a
REMOVED.txtin the Cardinal folder (~/.config/cardinal, or%APPDATA%\Cardinalon Windows) saying when and why. - Deletes the runner, its key file and its working folder. The runner log, if there is one, stays so you can read it.
- Removes the login item (the launchd item on a Mac, the systemd user service on Linux, the Scheduled Task named Cardinal runner on Windows) and stops the runner.
If the key file is already gone, only the login item and the runner's files are removed, your Claude settings are left as they were, and REMOVED.txt says so. Then open your Claude settings file and remove by hand anything that mentions Cardinal: under env, the CLAUDE_CODE_ENABLE_TELEMETRY, OTEL_... and CARDINAL_SETUP_VERSION entries, and under hooks, the SessionEnd entry whose address ends in /api/hooks/session.
Revoke the key
Every install line carries its own key. Open your member page (Team, then your name) and press Revoke next to the key for that computer. Until you do, anything still holding the key could send usage for you. If the workspace's access has ended, its keys are already revoked.