Configuration

/prism:setup writes everything Prism needs to ~/.prism/config.json. Most people never open that file. This page covers what’s in it, and the two values you can change.

Config file

{
  "apiKey": "prism_your_key_here",
  "show_realtime_summary": false
}

Field	Type	Default	Can you change it?
show_realtime_summary	boolean	false	Yes
ingest_url	URL	—	Yes, but read Pointing at another Prism first
apiKey	string	—	No — /prism:setup owns it
dashboard_url	URL	—	No — Prism resolves it from your key

The file is created with 600 permissions (owner read-write only) inside a 700 directory.

Note

~/.prism/config.json is shared by every version of the plugin installed on the machine, including a copy pinned to one project that never gets updated. That’s why Prism only ever adds fields to it and never renames or reuses one.

Viewing and changing settings

/prism:config             # show current values
/prism:config help        # every field, its default, and what changing it does
/prism:config set show_realtime_summary true
/prism:config unset ingest_url

/prism:config lists only the fields you’re allowed to change. apiKey and dashboard_url are managed for you and stay out of it.

API key

Your prism_* key authenticates the plugin with Prism. It’s provisioned for you automatically, and the Connect panel in your dashboard header hands you the setup command with the key filled in:

/prism:setup prism_YOUR_API_KEY

Re-run /prism:setup any time you need to rotate the key. Don’t edit apiKey by hand — see below for why.

Realtime summary

With show_realtime_summary on, Prism prints a short summary in your terminal after a turn completes. It is off by default; the full picture is on the dashboard either way.

/prism:config set show_realtime_summary true

Pointing at another Prism

ingest_url decides where your telemetry, prompts, and reports go. You would only change it to point at a Prism you run yourself.

Your key is sealed to the Prism it was issued for. Change ingest_url on its own — by hand or with /prism:config — and the plugin notices the mismatch locally and stops sending, rather than shipping your data somewhere the key doesn’t belong. /prism:status and /prism:doctor both report it.

The right way to move to a different Prism is to run /prism:setup again with a key from that Prism; it sets both values together.

Restart Claude Code after changing ingest_url.