This guide walks an admin through running a small pilot of Claude Code token tracking - typically a cohort of ~10 employees on a one-liner manual install - before a company-wide rollout. About 10 minutes start to finish.

Why pilot first? A manual install on a handful of employees confirms telemetry flows end-to-end and shows up in your dashboard before you push the same config to every machine via MDM.

1. Open your install page

Go to https://app.toriihq.com/team/ai/telemetry/claude-code. The URL auto-redirects to your org.

You'll land on the Telemetry index - click into Claude Code:

2. Copy the install one-liner

Under Manual setup, copy the install command - your token is already filled in (the endpoint is baked into the script itself). Three OS variants are shown; copy whichever ones your team uses:

• macOS: curl … install-claude-code-telemetry-macos.sh | bash -s -- …
• Linux: same but -linux.sh
• Windows (PowerShell): iwr … -OutFile … ; & … -Token '…'

3. Forward to your pilot employees

Paste it into a Slack message with this template:

Hey team - you're part of a small pilot for Claude Code telemetry. Please paste the line below into your terminal (PowerShell on Windows). No sudo, no restart, ~30 seconds. Then close any open Claude Code session and start a new one to pick up the new config.

<paste the one-liner here>

4. Confirm data is flowing

Back on the install page, click View recent events (top-right of the status card). You'll see a live per-employee table of events with timestamps, models, and OK status - the most direct signal that everything's wired up correctly.

The page-level status badge also flips to Active - last event … within a few minutes of the first event.

Rolling back

If anything looks off on a specific employee's machine, two clean options:

Preferred - run the uninstall one-liner. On the same install page, switch the operation from Install to Uninstall and copy the command. Pasting it in terminal strips only the telemetry env keys we added; nothing else in the employee's settings file is touched. Works on macOS, Linux, and Windows.

Manual restore from the install-time backup. Each install that changes an existing settings file drops a timestamped backup next to it:

• macOS / Linux: ~/.claude/settings.json.ai-otel-backup-<timestamp>
• Windows: same name under %USERPROFILE%\.claude\

Renaming that file over settings.json reverts to the exact pre-install state.

Most common gotcha

“I ran the command but no data shows up” → telemetry only emits from a new Claude Code session started after the install. Fully close any open Claude Code window/tab and open a fresh one before checking.

What’s next

Once the pilot is healthy and data is flowing, plan the company-wide rollout via your MDM. The Torii install page has an MDM rollout mode (toggle “Deployment method”) with ready-made scripts for Jamf, Kandji, Intune, JumpCloud, Mosyle, Workspace ONE, and SCCM.

Related articles

• What is LLM token tracking and why it matters
• Browse the full AI Module section for token rotation, troubleshooting, and uninstall guides.