Skip to content

CLI settings and files

Environment variables and files you can use to control the Prism CLI.

The CLI has no settings command. You switch collection on and off with the commands in Commands, and with the environment variables below.

Variable Effect
PRISM_OFF=1 The Prism hooks of the CLI and the plugins record nothing for the Claude Code or Codex session started with it, for example PRISM_OFF=1 claude or PRISM_OFF=1 codex. Other values have no effect.
PRISM_HOME An absolute path that replaces the Prism folder (see Files below) for every prism command and the background sender: local state, the token file, the object folder, and the installed versions. An empty or relative value is an error. Set it before prism setup, so the hook commands it writes follow it.
PRISM_SECRET_STORE With the value file, the sign-in token is stored in a file in the Prism folder that only your user can read, instead of the macOS Keychain.
CLAUDE_CONFIG_DIR Claude Code’s own variable. When prism setup runs in an environment where it is set and not empty, it registers hooks in the settings file of that directory instead of ~/.claude/settings.json and remembers the directory. prism setup remove, prism status, and prism uninstall act on every remembered directory. To add another profile, run prism setup once more in that environment.
CODEX_HOME Codex’s own variable. When prism setup runs in an environment where it is set and not empty, it registers hooks in the settings file of that directory instead of ~/.codex/config.toml and remembers the directory. Remembered directories and adding another profile work as for CLAUDE_CONFIG_DIR.

PRISM_OFF=1 affects only the process that inherits it. To switch collection off for good, use prism setup remove or prism uninstall. See Data collection and visibility.

prism login --server <address> sets the address of the Prism service. The CLI keeps it for later logins. The address must start with https://; http:// is accepted only for this computer. An address with a user name or password in it is refused.

Path Content
~/.claude/settings.json Claude Code’s settings. prism setup adds its hooks and prism setup remove takes exactly those out. Nothing else in it is touched, and the Prism plugin’s entries in enabledPlugins stay as they are.
~/.codex/config.toml Codex’s settings. prism setup adds a marked block of hooks and the trust records, and prism setup remove takes exactly those out. Nothing else in it is touched, and the plugin’s entry under [plugins."prism@optra-prism"] stays as it is.
~/.config/optra-prism/ (macOS and Linux), %APPDATA%\optra-prism (Windows) The Prism folder: everything else the CLI and both plugins keep. They share it, so one computer is one device and signs in once. On macOS and Linux, optra-prism inside the folder that XDG_CONFIG_HOME names replaces the first path when that variable is set to an absolute path. Only your user can read it.
state.db (in the Prism folder) Local state: records waiting to be sent and what Prism has read so far. Do not edit it.
credentials The sign-in token, only when the system secret store (the macOS Keychain, the Windows Credential Manager, or the Linux secret store) cannot be used or PRISM_SECRET_STORE=file is set.
flush.log Notes about dropped records and skipped sessions, with ids and counts only.
objects, shim, versions, current Private copies of changed files for statistics, and the installed versions the hooks run.
~/.prism/ Where the earlier Prism plugin kept its files, including its key. The CLI and the current plugins keep nothing there, and prism uninstall leaves it alone. /prism:setup in the Claude Code plugin lists the earlier plugin’s entries and removes them after you agree.

prism status prints your email address and device name; remove them if you do not want to share them. prism uninstall removes the files that the CLI created in the Prism folder.