Collect Cowork cloud sessions
Upload the Tokenize plugin to Claude so Cowork cloud sessions send prompts, tool calls, and subagent usage to Tokenize.
Cowork's own telemetry from cloud sessions leaves out prompt, response, and tool text. The Tokenize plugin runs inside each Cowork cloud session and sends that session's telemetry to Tokenize, including prompts, tool calls, and subagent usage. You set it up once for your whole organization in the Cowork cloud sessions section of Settings → Providers.
Who can do this: Admins. In Claude, you need a Team or Enterprise plan and an organization Owner.
The plugin works alongside Cowork OTel. Setting up both lets Tokenize tell you when cloud sessions are running without the plugin.
Step 1: Download the plugin
- Go to Settings → Providers and scroll to Cowork cloud sessions.
- Click Build plugin. Your browser downloads
tokenize-cowork-telemetry.plugin.
The file holds an ingest key for your organization. It can only send telemetry into your organization, but treat it like a password: anyone with the file can send data that looks like yours until you rotate the key. The section shows the start of the key and when it was made.
Building again reuses the same key, so the copy already in Claude keeps working.
Step 2: Upload it for the whole organization
In Claude, open the Plugins page and upload tokenize-cowork-telemetry.plugin. Then click Publish to org so every member gets it.
Step 3: Allow the plugin to reach Tokenize
Cloud sessions can only reach hosts on your allowlist. In Claude, open Organization settings → Capabilities → Code execution → Allow network egress → specific domains, and add this host:
ingest-http.otel.tokenizehq.com
Only sessions started after you save this can send.
Step 4: Check that it reports
Back in Cowork cloud sessions, click Check again. The status line tells you where things stand:
| Status | What to do |
|---|---|
| "Plugin installed and reporting." | Nothing. The section also shows how many sessions sent data in the last 7 days and when the latest send arrived. |
| "No data from the plugin yet." | Start a new cloud session after steps 2 and 3, then check again. |
| "Cloud sessions seen, but none reported by the plugin in 7 days. Check the plugin upload and the egress allowlist." | Make sure the plugin is published to the organization and the host is on the allowlist. |
| "No data since this key was made. Build the plugin and upload the new file." | The key was rotated. Repeat steps 1 and 2. |
| "The plugin's key was revoked. Build the plugin and upload the new file." | The key was revoked in Settings → API keys. Repeat steps 1 and 2. |
Tokenize can only spot cloud sessions the plugin missed when Cowork OTel is also set up. Without it, no data can mean either that nobody used cloud sessions or that the plugin can't reach Tokenize.
Rotate the key
Click Rotate key and confirm. The plugin already uploaded to Claude stops sending within a minute and keeps failing until you build the plugin again and upload the new file. Rotate if the file was shared with someone who shouldn't have it.
Troubleshooting
"The latest send couldn't tell who was signed in to the cloud session, so the plugin held back tool calls and prompts." The plugin couldn't identify the person, so it sent usage without text. Cowork's own telemetry still records the session, without text.
"Before its latest send got through, the plugin hit this error: …" An earlier send failed and a later one succeeded. If it keeps appearing, check the egress allowlist.
"The plugin build is unavailable right now." Tokenize has been alerted. Try again later.
"Your role does not include API key management." Ask an admin to set up the plugin.