Quickstart
Connect Claude Code or Codex and confirm your first activity.
You need a Prism account and Claude Code or Codex on the same computer. On macOS you can connect with the CLI (recommended), the Claude Code plugin, or the Codex plugin. On Windows and Linux you connect with the plugins, because the CLI can be installed on macOS only. A plugin needs no CLI, and each plugin records only its own tool. You need only one way. Read Data collection and visibility before connecting.
Open the Install guide
Section titled “Open the Install guide”- Sign up in the Prism web app. You must agree to the terms to create the account, and a confirmation mail goes to your address. Only an account with a confirmed address can approve a device in the sign-in step below. If you sign up with Google, GitHub, or Microsoft, there is no confirmation mail.
- Open Connect in the header. The Install guide screen opens, and under Connect Claude Code and Codex the operating system of your computer is already selected. Select another system if the selection is wrong.
- Choose a tab under Way to connect. On macOS the tabs are CLI (marked as recommended), Claude Code plugin, and Codex plugin. On Windows and Linux the CLI tab is not shown, and the screen says that the CLI can be installed on macOS only.
A computer signs in once. The CLI and both plugins share one sign-in, so if this computer is already signed in through the CLI or the other plugin, you can skip the Sign in step of a plugin.
The steps below have the same names and the same order as on the screen.
Connect with the CLI
Section titled “Connect with the CLI”The CLI is for macOS. Run every command of this section in a terminal.
-
Install the CLI
Copy the command from the Install script tab, or from the Homebrew tab if you use Homebrew, and run it. Prism’s pages do not quote the command because it can differ between deployments.
-
Sign in from the terminal
Copy the command shown in this step and run it:
Terminal prism loginThe terminal prints an address and a code. Prism opens the address in your browser unless you are connected over SSH. Check that the code on the Approve device screen matches the one in the terminal, then select Approve. The code is valid for 10 minutes. When the terminal prints
Logged in. The token is stored in the macOS Keychain., the sign-in is complete. -
Start recording
Choose one of the two ways. The step does not need both.
Record per session
Start the sessions you want recorded with
prism claudeinstead ofclaude, and withprism codexinstead ofcodex. Options go after it unchanged, soclaude --resumebecomesprism claude --resume. Only sessions started this way are recorded.Terminal prism claudeprism codexRecord every session
Run
prism setuponce in a terminal. It registers Prism’s hooks in the settings of each of Claude Code and Codex that it finds on your computer, and it skips a tool it does not find. Every session you start withclaudeorcodexafter that is recorded. If you switch settings folders withCLAUDE_CONFIG_DIRorCODEX_HOME, runprism setuponce for each folder you use, for exampleCLAUDE_CONFIG_DIR=<folder> prism setuporCODEX_HOME=<folder> prism setup. One run applies to one folder.Terminal prism setup
prism setup is a choice, not a required step. Commands describes both ways in detail.
Connect with the Claude Code plugin
Section titled “Connect with the Claude Code plugin”-
Install the plugin
Choose where you install it.
Start Claude Code and type these two commands into its prompt, in order:
Claude Code /plugin marketplace add grumatic/optra-prism-plugin/plugin install prism@optra-prismRun these two commands in a terminal, in order. If Claude Code was open, close it and start it again afterwards.
Terminal claude plugin marketplace add grumatic/optra-prism-pluginclaude plugin install prism@optra-prism -
Sign in
Type this into the Claude Code prompt:
Claude Code /prism:setupClaude Code shows an address and a code. Open the address in a browser and approve if the code on the page is the same. If this computer is already signed in through the CLI or the Codex plugin, you do not need this step.
When the deployment you use has a service address other than the built-in one, the Install guide screen shows in this step the command that starts Claude Code with
PRISM_SERVER_URLset. Start Claude Code with that command, then sign in. -
Check
Start Claude Code again, send one message, then type this into the prompt:
Claude Code /prism:statusA time on the
Last triggerline means recording works. Sessions started after you sign in are recorded.
Connect with the Codex plugin
Section titled “Connect with the Codex plugin”-
Install the plugin
Run these two commands in a terminal, in order:
Terminal codex plugin marketplace add grumatic/optra-prism-plugincodex plugin add prism@optra-prism -
Trust the hooks
Start Codex and type this into its prompt:
Codex /hooksTrust all 4 of Prism’s hooks. Codex does not run a hook you have not trusted, so nothing is recorded for it.
-
Sign in
Type this into the Codex prompt. If Codex asks whether it may run a command, allow it.
Codex $prism:setupCodex shows an address and a code. Open the address in a browser and approve if the code on the page is the same. If this computer is already signed in through the CLI or the Claude Code plugin, you do not need this step. When the deployment you use has another service address, the screen shows in this step the command that starts Codex with
PRISM_SERVER_URLset. Start Codex with that command, then sign in. -
Check
Start Codex again, send one message, then type this into the prompt:
Codex $prism:statusA time on the
Last triggerline means recording works. Sessions started after you sign in are recorded.
Confirm your first activity
Section titled “Confirm your first activity”Open Claude Code or Codex, enter a prompt, and let it answer. The Welcome to Prism screen tracks three steps and updates by itself:
- Device connected: your sign-in was approved.
- First record arrived: the CLI or the plugin sent its first record.
- First prompt arrived: Prism received your first prompt.
When all three are done, the web app moves to Realtime. A score for the work can take longer: Prism evaluates work after the session ends, after /clear, or three hours after the last activity.
Run prism status in a terminal, or /prism:status in Claude Code, or $prism:status in Codex, at any time to see the sign-in, registration, and sending state. See Troubleshooting if a step does not complete.
Next steps
Section titled “Next steps”- Read Commands for what each
prismcommand does. - To stop collection for one session, start it with
PRISM_OFF=1 claudeorPRISM_OFF=1 codex. See Data collection and visibility. - To use the CLI and a plugin together, update, or remove Prism, read Install and update.
- Already using the earlier plugin? See Install and update.