OR Otel

or-otel sends usage from Claude Code (terminal and Claude Desktop) and Codex (terminal and desktop app) to OpenReason, so you can see usage and cost by organization, team, and user. Requests still go directly to Anthropic or OpenAI and are billed to your own subscription. To bill requests to your org and apply budgets instead, use claude-or.

Once set up, every Claude Code and Codex session on your Mac reports its model, token counts, and prompt text to OpenReason. To send usage without prompt text, see What gets sent.

Prerequisites

Requirement	Details
macOS	Linux and Windows coming soon
OpenReason API key	Starts with `sk-or_`. Create one at admin.openreason.app/dashboard/api-keys, or ask your admin
sudo access	Used to install `or-otel` and write the Claude Code and Codex config

Works with Claude Code and Codex whether they’re pre-installed or newly installed after setup.

Install

Run the installer

Open Terminal and run:

curl -fsSL https://get.openreason.app/otel | bash

Enter your password for sudo when asked. This installs or-otel to /usr/local/bin.
Paste your OpenReason API key when asked. Nothing shows while you paste — that’s expected.
Enter your sudo password again if asked. This writes the Claude Code and Codex config.

The installer checks your key against the router and ends with:

✓ Setup complete.

Restart your AI tools (required)

Usage isn’t tracked until you restart. Sessions left open from before setup keep their old settings.

Claude Desktop and Codex app: fully quit with Cmd+Q (closing the window isn’t enough), then reopen.
Claude Code and Codex CLI: open a new terminal window and start a new session.

Check it works

or-otel doctor

Every line should show ✓, ending with router accepts exports.Then send one prompt from each tool you use, in a new terminal:

claude -p "say hi"
codex exec "say hi"

Open Audit Log → Events in the OpenReason dashboard. New rows appear within about 30 seconds, with the model, token counts, and your prompt.

Install options

Pass options to or-otel setup after bash -s --, or set environment variables before bash:

Usage only, no prompt text

curl -fsSL https://get.openreason.app/otel | bash -s -- --no-log-prompts

Key up front (CI, MDM, scripted rollout)

curl -fsSL https://get.openreason.app/otel | OR_API_KEY=sk-or_... bash

A different router

curl -fsSL https://get.openreason.app/otel | OR_ROUTER_URL=https://<router-url> bash

Use OR_ROUTER_URL only if your admin gives you a router URL. The default is https://api.openreason.app.

What gets sent


Sent	Model, token counts, latency, session ID, your prompt text, and the reply
Not sent	File contents, tool output, anything outside Claude Code and Codex
Cost	A list-price estimate — Claude Code’s own, and for Codex the OpenAI API price of its tokens. Both count toward your team’s OpenReason budget. Anthropic or OpenAI still bills you on your own subscription, not OpenReason

Prompt and response text is redacted for secrets and kept up to 256k characters each. Longer text is cut and the row is marked truncated. To send usage only, without text:

or-otel setup --no-log-prompts

The choice is remembered across updates. Run or-otel setup --log-prompts to turn text back on.

Commands

Command	What it does
`or-otel setup [--router URL] [--log-prompts \| --no-log-prompts]`	Write the config. Keeps your saved key, router, and prompt setting unless you pass new ones
`or-otel status`	Check the key, both configs, and the Codex reply hook are present
`or-otel doctor`	`status`, plus installed tools, the last Codex hook run, and a test export to the router
`or-otel update`	Install the latest `or-otel` and re-apply the config
`or-otel uninstall [--yes]`	Remove the config, your saved key, and `or-otel` itself
`or-otel version`	Print the version

Update

or-otel update

Re-running the install command does the same thing. Both keep your saved key, router, and prompt setting.

Uninstall

or-otel uninstall

Confirms with [y/N], then removes the Claude Code and Codex telemetry config, your saved key (~/.openreason/otel), and or-otel itself. Claude Code and Codex stay installed and work as normal. Fully quit and reopen them afterwards.

Troubleshooting

✗ couldn't download or-otel

Check your network or VPN, and that the install URL is the one your admin gave you.

or-otel: command not found after install

Open a new terminal. /usr/local/bin is on the default macOS PATH. If you’ve changed yours, run the full path:

/usr/local/bin/or-otel doctor

✗ Key rejected (HTTP 401)

Setup shows rejected this key, or or-otel doctor shows router rejects the key. The key is invalid, revoked, or doesn’t match the router — for example, a development key against production.Create a new key at admin.openreason.app/dashboard/api-keys, then re-run setup and paste it:

or-otel setup

If your admin gave you a different router, add --router https://<router-url>.

✗ that doesn't look like an sk-or_ key

OpenReason API keys start with sk-or_. Copy the full key from admin.openreason.app/dashboard/api-keys and re-run or-otel setup.

✗ router unreachable

Check your network or VPN and retry. If it persists, tell your OpenReason admin — the router may be down.

✗ Claude Code config has no auth header

The config was written by an older or-otel. Update it:

or-otel update

doctor shows all ✓, but a tool isn't in the audit log

Fully quit (Cmd+Q) and reopen the tool, then start a new session. Terminals must be opened after setup to pick up the config.

⚠ an MDM profile is installed

Your company manages Claude Code or Codex centrally, and those settings take priority over or-otel. Ask your IT team.

For anything else, send the output of or-otel doctor to your OpenReason admin.

For admins

Where the config lives

or-otel setup writes each tool’s managed (admin) config. Managed config sits above the user’s own ~/.claude and ~/.codex settings, so it covers existing and future installs, and users can’t switch it off from their own settings.

Path	Contents
`~/.openreason/otel/`	Saved key, router, and prompt setting for re-runs (directory `0700`, files `0600`)
`/Library/Application Support/ClaudeCode/managed-settings.d/openreason-otel.json`	Claude Code `env`: OTLP logs exporter, `http/json`, `<router>/otlp`, auth header, `OTEL_LOG_USER_PROMPTS`
`/etc/codex/managed_config.toml`	An `[otel]` block between `# >>> openreason otel >>>` markers. Other managed Codex settings are kept
`/etc/codex/requirements.toml`	While text is sent: a `Stop` hook that runs `or-otel codex-hook` after each Codex turn to send its reply. Removed with `--no-log-prompts`

The managed config files hold the user’s key and are readable by other local accounts. On shared machines, push the same settings through MDM instead.

Unattended installs

Pass the key up front to skip every prompt except sudo:

curl -fsSL https://get.openreason.app/otel | OR_API_KEY=sk-or_... bash

MDM rollout

Skip the installer and deploy configuration profiles instead:

com.anthropic.claudecode — the same keys as the Claude Code JSON file above.
com.openai.codex — config_toml_base64 holding the [otel] block, and requirements_toml_base64 holding the Stop hook for Codex replies. or-otel must still be installed for the hook to run.

An MDM profile overrides the files or-otel writes. or-otel setup and or-otel status warn when one is installed.

Claude Team and Enterprise orgs

If your org sends any settings from the claude.ai admin console, Claude Code takes managed settings from there first. or-otel puts the auth header in env for this reason, because env is still merged from the local file.To have the whole local file apply, set "managedSourcesBehavior": "merge" in the claude.ai admin console.

Claude Code with OpenReason

Route Claude Code through OpenReason instead, so prompts bill to your org’s key and per-user budgets apply.

Get Started

Prerequisites

Install

Install options

What gets sent

Commands

Update

Uninstall

Troubleshooting

For admins

Next

Claude Code with OpenReason

​Prerequisites

​Install

​Install options

​What gets sent

​Commands

​Update

​Uninstall

​Troubleshooting

​For admins

​Next

Claude Code with OpenReason

Prerequisites

Install

Install options

What gets sent

Commands

Update

Uninstall

Troubleshooting

For admins

Next