Set up OpenTelemetry for Cowork, Claude Code, Codex, and Cursor

Send Cowork, Claude Code, Codex, and Cursor telemetry to Tokenize for your whole organization from each vendor's admin settings.

Cowork, Claude Code, Codex, and Cursor can each send OpenTelemetry (OTel) data straight to Tokenize. You set it up once in each vendor's admin settings, and it applies across your organization. The setup lives in Settings → Providers: Cowork OTel and Claude Code OTel in the Anthropic group, Codex OTel in the OpenAI group, and Cursor OTel in the Cursor group. Click a section title to open it. A check mark before a section's title means Tokenize received data from that tool's own OTel export in the last 7 days. Data sent by the Tokenize desktop app doesn't count toward the check.

Who can do this: Admins. You also need admin access to the tool you're configuring, listed below.

Each section follows the same three steps: create an ingest key, set up the vendor's side with the values shown, then apply.

Requirements

SectionWhat you need
Cowork OTelA Claude Team or Enterprise plan and organization admin access
Claude Code OTelA Claude Team or Enterprise Owner
Codex OTelA ChatGPT Enterprise workspace and access to Agent Security in the OpenAI Admin Console
Cursor OTelA Cursor Enterprise plan and a Cursor team admin

Codex OTel and Cursor OTel carry an Enterprise badge. Only ChatGPT Enterprise workspaces and Cursor Enterprise teams can set them up.

Step 1: Create an ingest key

  1. Go to Settings → Providers and open the section you want.
  2. Click Generate key.
  3. Copy the key and save it in your secret manager.

The key is shown once. You can't view it again later. Use a separate key for each tool, so you can revoke one without breaking the others. Revoke keys in Settings → API keys. See API keys.

If Generate key is disabled and you see "Ask someone with API key access to generate a key.", your role can't create keys. Ask an admin.

Step 2: Install the config

After you generate a key, the section shows the values to paste, with your key already filled in.

Cowork

Click Cowork monitoring in Claude to open Claude's monitoring settings, and set the three values shown:

  • OTLP endpoint
  • OTLP protocol: http/protobuf
  • OTLP headers: Authorization=Bearer followed by your key

Then, in the Office Agents section below it, click Copy settings from Cowork.

Claude Code

Click Open Claude Code admin settings. Under Managed settings, click Manage and paste the JSON in. It is an env block that turns on telemetry and points it at Tokenize. If you already have managed settings, add these env entries to them instead of replacing what is there.

Codex

Click Setup guide for OpenAI's instructions. In the OpenAI Admin Console, go to Agent Security and paste the [otel] config into the managed configuration.

Cursor

Cursor's servers send usage for the whole team, so the setup lives in Cursor's team settings, not on each computer.

  1. In Cursor, open Team Settings → OpenTelemetry Export and create a destination with the values the section shows: the Destination URL, the Auth header name Authorization, and the Auth header value, which is Bearer followed by your key. Click Cursor setup guide for Cursor's own instructions.
  2. Click Test connection to check the URL and header, then click Enable. Cursor starts sending within about a minute.
  3. To include conversations, turn on Allow conversation content export in Team Settings → OpenTelemetry Export. It sits above the destination family toggles. Cursor confirms with "Conversation content export enabled."
  4. On the destination, turn on Conversation content. Three toggles appear under it: Prompts, Responses, and Tool I/O. Turn on all three.
  5. If your team uses Grok Bot, a Cursor admin turns on Grok Bot Action Recording in Grok Bot settings in the Cursor dashboard. Click Open Grok Bot settings in the Cursor OTel section to open it. See See Cursor Grok Bots.

Usage that arrives this way shows as Cursor across the dashboard, with Cursor's own cost figures.

Step 3: Apply

  • Cowork: save your settings, then start a new Cowork session.
  • Claude Code: users approve the change the next time they start Claude Code.
  • Codex: the config applies the next time users start Codex.
  • Cursor: nothing to restart. Cursor sends once the destination is enabled.

What gets sent

By default, these configs send prompt content to Tokenize. Change the config before you paste it if you don't want that.

  • Claude Code sends prompts, responses, and tool content. Remove the OTEL_LOG_* lines to leave them out.
  • Codex sends prompt text. Remove log_user_prompt to leave it out.
  • Cowork content follows Claude's monitoring settings.
  • Cursor sends conversation content only when you turn it on in Cursor, as in the Cursor steps above.

Cowork OTel from cloud sessions leaves out prompt, response, and tool text. To collect it, add the Tokenize plugin. See Collect Cowork cloud sessions.

For how Tokenize handles this data, see Privacy and redaction and What data Tokenize collects.

Troubleshooting

  • "Couldn't generate a key. Try again." The key wasn't created. Click Generate key again.
  • "Your role does not include telemetry setup." Your role can't set up OTel. Ask an admin.
  • No data after setup: make sure people started a new session after the change. Claude Code users must approve the managed settings change first.
  • No data from Claude Code cloud sessions: check the endpoint in your managed settings. It should be https://ingest-http.otel.tokenizehq.com, with no port. Older configs pointed at ingest.otel.tokenizehq.com:4318, which cloud sessions can't reach. Copy the config again from Claude Code OTel and replace it. Do the same for Codex.
  • No data from Cursor: in Cursor's OpenTelemetry Export settings, check that the destination is enabled and that Test connection passes with the Destination URL and header from the Cursor OTel section.

Network access

The Cowork, Claude Code, Codex, and Cursor configs all send to ingest-http.otel.tokenizehq.com over HTTPS on port 443. If a firewall or proxy sits between your users and the internet, allow that hostname. Cursor sends from its own servers, so no firewall change is needed on your users' computers for Cursor OTel.