Opaline

Opaline is team-wide, message-level analytics for Claude Code and Codex: it gathers session traces so you can see who is stuck in which repo, how many tokens and hours were spent, and which skills were used — turning teammate struggle into something the rest of the team can learn from.

The site line is “Pull back the curtain on your coding sessions,” closer to PostHog for coding-agent runs than to another IDE. A CLI repo (opalinehq/cli) is used to collect sessions.

Highlights:

• Message-level detail, not just a monthly invoice total;
• Slices by teammate and repository for cost, duration, and skill adoption;
• Aimed at engineering orgs already running Claude Code / Codex at team scale;
• Site: https://opaline.so .

Why it matters

Coding agents are becoming a default team tool, yet most orgs only see a vendor bill — not which tasks are expensive or which prompts keep failing. Opaline adds that observability layer, unlike IDE plugins or proxy gateways alone.

Limits

Public materials focus on Claude Code and Codex; other agents depend on the live integrations list. Session traces are sensitive engineering data — check retention, access control, and whether anything leaves your machine or tenant before you roll it out.

1. Open https://opaline.so and create a team workspace;
2. Install the CLI or collector from the docs and hook it to Claude Code / Codex sessions;
3. In the console, slice cost, duration, and failure modes by person, repo, and skill;
4. Turn recurring stuck points into team norms or skills, then compare later sessions.