Installation overview
Cost Intelligence is delivered as a Claude Code plugin that runs a local proxy on each developer machine. Rolling it out means doing two things: getting the plugin enabled, and pointing it at your Opik workspace.
Nothing needs to be installed on a server, and there is no per-developer manual step in any of the supported paths.
Choose a rollout path
Recommended. Push config with the tooling you already run (Jamf, Kandji, Intune, JumpCloud) and choose exactly which devices or groups get it, so you can pilot and stage the rollout.
Simplest. One JSON paste in the Claude admin console, but it applies to every authenticated user in the org, all at once.
Transparent capture via a system extension, for when no client configuration can be delivered at all.
Which one fits:
We recommend MDM for most organizations. It uses the device tooling admins already run day to day, and it lets you decide who gets the rollout: start with one team, confirm data is landing the way you expect, then widen. Managed settings has no targeting: it applies to every authenticated user in the organization the moment you save it, which makes a pilot impossible and a mistake org-wide.
Choose managed settings when you have Claude for Teams or Enterprise, want the fastest possible path, and are happy enabling everyone at once, or when your developers’ machines aren’t centrally managed at all. Reach for the macOS app only when neither path can deliver client configuration.
Try it on your own machine first
Before pushing anything to a fleet, install it on your own machine. It takes a minute, it proves your workspace credentials actually work, and it gives you a known-good reference to compare against if a fleet rollout later looks wrong.
From inside Claude Code:
Point it at your workspace with the values from the configuration reference below, in ~/.opik-cipx/config.toml, then restart Claude Code. The session hook starts the daemon and routes the agent through it.
Run a short session, then check what happened:
opik-cipx viewer is the fastest way to answer “is it capturing what I
expect?”. It renders each captured request with every region coloured by the
cost bucket it landed in, on your own machine, before anything ships. It is
also the first place to look if numbers in the dashboard ever look wrong.
Finally, confirm the traces arrived in your Opik workspace. Once you have seen that work once, a fleet rollout is the same configuration delivered by a different mechanism.
What you’ll need
Before starting any path:
An Opik workspace for coding-agent data
Use a dedicated workspace rather than a shared one. It keeps fleet-wide agent traffic isolated from individual developers’ own Opik projects.
You don’t have to assemble this yourself. Email sales@comet.com with the rollout path you’re taking and we’ll send back the exact configuration snippet for your workspace, filled in and ready to paste into your admin console or MDM. It’s the fastest way to get a first pilot running, and it removes the most common source of rollout errors.
Configuration reference
Every path sets the same four values; only the delivery mechanism differs.
Optional:
Data collected
Only counts, costs, and structural metadata are reported. Prompt and response content is not collected unless content capture is explicitly enabled, and an organization can pin that off so no individual user can turn it on.
Verify a rollout
On a target device, in a fresh Claude Code session:
Then confirm traces are arriving in the target Opik workspace. That last check is the one that matters: a device can look fully installed and still be shipping nothing if the workspace credentials didn’t land.