Cardinal by RAMCOREOpen Cardinal

What the installer changes on your computer

Setup on your computer. Exactly which files the install line writes and which Claude settings it adds.

The install line changes a small, fixed set of things. It never touches your Claude login, keychain or API keys.

Files it writes

On a Mac:

  • ~/.config/cardinal/cardinal-runner.mjs: the launcher, a small file that starts the runner. cardinal-runner-core.mjs beside it is the runner itself, with no dependencies. When a new version is installed, the previous one is kept as cardinal-runner-core.prev.mjs, with update-state.json beside them.
  • ~/.config/cardinal/runner.json: your Cardinal address, your member key, and where claude is. Readable only by you.
  • ~/Library/LaunchAgents/dev.ramcore.cardinal.runner.plist: the login item that keeps the runner going.
  • ~/.config/cardinal/runner.log: the runner's log.

On Windows:

  • %LOCALAPPDATA%\Cardinal\cardinal-runner.mjs: the launcher. cardinal-runner-core.mjs beside it is the runner itself, with its previous version and update notes next to it.
  • %APPDATA%\Cardinal\runner.json: your Cardinal address, member key and where claude is.
  • A Scheduled Task called "Cardinal runner", for your user only.

The runner also keeps a runner-work folder next to runner.json for temporary job files. Each job's files are removed when it ends.

Updates

The runner updates itself. A new version is signed by Cardinal and your computer checks the signature before it installs anything, only from your Cardinal address over HTTPS, and only while no job or chat is running. It keeps the previous version, and if the new one fails to start three times, it goes back. The owner's own computers take a new version first; everyone else gets it after a day of clean running. An owner can choose "Ask me first" under Runner updates in Settings › Tracking, sync and data and press Update when they are ready; Today then tells the owner an update is waiting. If a computer could not update, Today tells that person to run the install line again.

Claude settings it adds

Your Claude Code user settings file is ~/.claude/settings.json on a Mac and %USERPROFILE%\.claude\settings.json on Windows. The installer merges in:

  • Telemetry settings under env: CLAUDE_CODE_ENABLE_TELEMETRY, the OTEL_... exporter settings that point at your Cardinal with your key, and CARDINAL_SETUP_VERSION.
  • One SessionEnd hook that tells Cardinal when a session closed and in which folder.

Everything else in the file is kept. Before writing, it saves a copy next to the file, named settings.json.cardinal-backup- followed by the date and time. If your file has a JSON error, it stops and changes nothing, and tells you the line number.

What is not sent

Cardinal never sets the options that would log prompt or response text, so none is sent. The session-end hook carries no prompt text either.

The Claude app and VS Code

The Claude app's Code tab and the VS Code extension run Claude Code, which reads the same settings file, so their sessions are counted too. The app's chat and Cowork sides don't read these settings on individual plans; on Claude Team or Enterprise, your admin turns on telemetry in the admin console instead.