Skip to content

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.

  1. 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.
  2. 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.
  3. 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.

The CLI is for macOS. Run every command of this section in a terminal.

  1. 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.

  2. Sign in from the terminal

    Copy the command shown in this step and run it:

    Terminal
    prism login

    The 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.

  3. 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 claude instead of claude, and with prism codex instead of codex. Options go after it unchanged, so claude --resume becomes prism claude --resume. Only sessions started this way are recorded.

    Terminal
    prism claude
    prism codex

    Record every session

    Run prism setup once 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 with claude or codex after that is recorded. If you switch settings folders with CLAUDE_CONFIG_DIR or CODEX_HOME, run prism setup once for each folder you use, for example CLAUDE_CONFIG_DIR=<folder> prism setup or CODEX_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.

  1. 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-prism
  2. Sign in

    Type this into the Claude Code prompt:

    Claude Code
    /prism:setup

    Claude 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_URL set. Start Claude Code with that command, then sign in.

  3. Check

    Start Claude Code again, send one message, then type this into the prompt:

    Claude Code
    /prism:status

    A time on the Last trigger line means recording works. Sessions started after you sign in are recorded.

  1. Install the plugin

    Run these two commands in a terminal, in order:

    Terminal
    codex plugin marketplace add grumatic/optra-prism-plugin
    codex plugin add prism@optra-prism
  2. Trust the hooks

    Start Codex and type this into its prompt:

    Codex
    /hooks

    Trust all 4 of Prism’s hooks. Codex does not run a hook you have not trusted, so nothing is recorded for it.

  3. Sign in

    Type this into the Codex prompt. If Codex asks whether it may run a command, allow it.

    Codex
    $prism:setup

    Codex 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_URL set. Start Codex with that command, then sign in.

  4. Check

    Start Codex again, send one message, then type this into the prompt:

    Codex
    $prism:status

    A time on the Last trigger line means recording works. Sessions started after you sign in are recorded.

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.