Commands Reference

/prism:setup

Configure your API key and activate telemetry.

/prism:setup prism_YOUR_API_KEY

It takes exactly one argument — your key. There are no scope flags; setup detects the scope the plugin was installed in and writes only that scope’s settings file.

New keys start with prism_ (provisioned automatically; the Connect panel in the dashboard header shows the setup command with your key already in it); the legacy gck_ prefix is still accepted.

What it does:

Stores your key in ~/.prism/config.json (owner-only) and resolves the Prism it belongs to.
Ties the key to that Prism, so a later edit to apiKey or ingest_url on its own is caught rather than silently sending your data elsewhere.
Detects the scope the plugin is installed in and writes the OTEL env vars — including the prism_*-embedded OTEL_EXPORTER_OTLP_HEADERS — to that scope’s settings file:
- user → ~/.claude/settings.json
- project → $CLAUDE_PROJECT_DIR/.claude/settings.json (committed to git)
- local → $CLAUDE_PROJECT_DIR/.claude/settings.local.json (gitignored)

See Installation Scopes for the full scope rules.

Restart Claude Code afterwards — OTEL env vars are read at process start, so a running session won’t pick them up.

/prism:status

Show connection health, scope, and toggles.

/prism:status

Displays:

API key prefix (e.g. prism_abc12…), or a setup prompt if missing.
Config scope — user, project, both, or none. Warns if OTEL vars appear in the shared .claude/settings.json, which indicates a prism_* key may have been committed.
Endpoints — the ingest URL and the OTEL logs/metrics endpoints actually in effect.
Settings — each value’s current setting and which file it came from.
Key binding — whether your key still matches the Prism it was issued for.

To change a setting, use /prism:config.

/prism:config

Show or update Prism runtime configuration.

/prism:config

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

It lists only the fields you can change — show_realtime_summary and ingest_url — with each one’s current value, default, accepted values, and whether the change needs a restart. apiKey is managed by /prism:setup and dashboard_url comes from the server, so neither appears here.

See Configuration for what each field controls.

/prism:doctor

Diagnose Prism plugin configuration and connectivity issues.

/prism:doctor

Runs four checks and prints a summary table:

#	Check	What it verifies
1	API Key	A `prism_*` key is present in `~/.prism/config.json` and still bound to its Prism
2	OTEL Settings	OTEL env vars are written to the right `.claude/settings.json` scope and match disk
3	Ingest Health Endpoint	The ingest endpoint responds to a health probe
4	OTEL Headers Helper	The on-disk headers-helper setting and artifact are in a safe state

Each check returns PASS, WARN, or FAIL, with the remediation for anything that didn’t pass. It also reports whether debug logging is on and which file it writes to.

If everything passes, you’ll see: All checks passed. Your Prism configuration is healthy.

/prism:realtime

Show the current session’s realtime Prism score summary.

/prism:realtime

Displays a snapshot of the session you’re in right now — its live grade, accumulated cost, and turn count — so you can gauge how the session is going without leaving the terminal or opening the dashboard.

Unlike /prism:report (a weekly rollup across sessions), this focuses on the live session only.

/prism:report

Weekly review — this week vs last week, Prompt Score with letter grade, habits, worst prompts.

/prism:report

If no report exists for the period yet, the command offers to generate one — that takes up to about two minutes — and then shows it.

Displays:

Comparison — this week vs last week: Prompt Score with letter grade, sessions, cost, and tokens, plus Skill / Speed / Efficiency when the report has them. Each row shows the week-over-week delta.
Token usage — where your tokens went this period.
Habits — average turns per session, median response time, and multi-clauding events.
Worst prompts — the lowest-graded prompts, each with its session, turn index, and a preview.
Coaching — short coaching notes tied to your weakest habits.
Cost optimization — total cost, wasted cost and its share, potential savings, and the top rightsizing or waste actions.

It closes with a “what changed most” line, a single focus-area recommendation, and a link to the full dashboard report.

/prism:help

List all /prism:* commands grouped by category.

/prism:help

Output is grouped into Setup & Config, Configurable fields, Review, and Automatic (hooks — no command needed), followed by a short getting-started block and links to the dashboard setup page and docs.

/prism:uninstall

Remove the plugin, configuration, and telemetry settings.

/prism:uninstall

It runs in two steps — a preview, then the removal.

Preview. It reads your setup and shows exactly what it would remove: the scope it’s installed in, the settings file it would edit, and the OTEL values it owns. Nothing is changed yet.
Apply. Confirm and it re-checks every one of those targets immediately before touching it. If anything has changed since the preview, it stops without making a single edit.

It removes only Prism-owned targets in the scope you’re uninstalling from. Another Prism install — a different project, a pinned older version — keeps its registration, config, data, and cache. A value that has drifted from what Prism wrote is preserved rather than overwritten.

Restart Claude Code afterwards. Telemetry stops and the hooks deactivate; your dashboard data is unaffected.