Skip to content

Plugin Overview

The Prism plugin runs inside Claude Code with six automatic hooks and eight slash commands. The hooks run silently in the background; the commands are on-demand.

These run without any commands — they’re always active once the plugin is installed:

HookTriggerWhat it does
SessionStartSession beginsChecks your API key and the OTEL settings, and reports what it found
UserPromptSubmitBefore each promptCaptures the prompt to Prism
CwdChangedYou switch working directoryKeeps the session’s project context accurate
PostCompactAfter /compactResets the per-compaction session state
PostToolUseAfter a SendMessage tool callCaptures git and prompt “evidence” that links your changes to the prompt that drove them
StopAfter each responseSends the response and the turn’s metadata to Prism

The hooks never block your prompt — if anything fails, the prompt still goes through.

What the plugin does not do in your terminal

Section titled “What the plugin does not do in your terminal”

It does not score your prompt locally, and it does not print coaching lines or rewrite suggestions. Scoring runs on the server after the prompt is captured, and coaching surfaces on the dashboard.

The one thing it can print is a short realtime summary after a completed turn, and that is off unless you turn it on:

Terminal window
/prism:config set show_realtime_summary true

Run these explicitly during a session:

CommandPurpose
/prism:setup [key]Configure your API key and enable telemetry
/prism:statusConnection health, install scope, and what’s configured where
/prism:configShow or update the settings you can change
/prism:doctorDiagnose configuration and connectivity issues
/prism:realtimeThis session’s live summary (grade, cost, turns)
/prism:reportWeekly review — this week vs last week, Prompt Score, habits, worst prompts
/prism:helpList all commands
/prism:uninstallRemove Prism’s settings and OTEL config

See Commands for the detailed reference.

The plugin does not ship in-terminal prompt coaching, prompt rewrites, or an always-active advisor. Analysis runs on the server after each prompt is captured, and the results surface on the dashboard:

  • Inline annotations in session replay — which prompt-rubric checks failed, and why
  • Coaching cards on your personal report
  • The Task advisor on the Realtime view — per sub-session, with an example rewrite
  • Advisor & Summaries

The plugin stores its config at ~/.prism/config.json, and that file is the only place it reads settings from. Two values are yours to change:

FieldPurpose
show_realtime_summaryPrint a short summary in the terminal after a turn. Off by default.
ingest_urlWhich Prism to talk to. Only relevant if you run your own.

apiKey and dashboard_url are also stored there but managed for you — /prism:setup owns the key, and the dashboard address comes from the server. See Configuration.