Pull back the curtain on your team's claude code and codex sessions.
Track token cost, time, and skill usage for every single message across your team’s sessions.
Catch every “You’re absolutely right” from Claude and every “I know, you fucking idiot” from a frustrated teammate.
This is the 3rd launch from Opaline. View more
Opaline
Launched this week
Team-wide, message-level analytics for Claude Code and Codex sessions.
Track token cost, time, and skill usage for every single message across your team’s sessions.
Catch every “You’re absolutely right” from Claude and every “I know, you f*cking idiot” from a frustrated teammate.
Free Options
Launch Team
Tested it and actually gave me some interesting insights
Opaline
@lukas_bormann nice thanks man!
Laserfocus
as Evren mentioned, the origins of this was as an internal tool. We identified quite some issues in our skill usage across the team, to really improve and streamline the output across the team with agents.
Opaline
@marc_hoffl yes sir 🫡
Macaly
tracking every you're absolutely right moment per session is kinda genius, usefull for eng leads 😂
Skill usage is the metric I'd look at first. I have a lot of skills in my setup and I honestly don't know which ones actually fire and which ones just sit there. Can Opaline show skills that were loaded but never used?
Opaline
@wwenioaguiar great take. actually working on it as we speak :)
Dude this i literally EXACTLY what i needed.
Opaline
@jaye_temenu appreciate it!
Nice launch. Question from how we run agents on our team: a growing share of our usage isn't interactive, it's headless runs in CI (claude -p, codex exec) kicked off on every PR. Does Opaline ingest those non-interactive sessions too, and how do you attribute them? A CI runner isn't a team member, but that's often where a big chunk of the token spend actually goes.
Opaline
@pratap_kumar5 ci wasn't a focus until now so we'll need to fix this. codex exec works if you configure the hook to it but claude -p does not. thank you for the heads up. issue is opened
@evrendombak Thanks evren - good to know the codex exec hook works, will give that a try in the meantime. Happy to test the claude -p side once your fix lands if that's useful.
Dial
the "catch every frustrated message" framing is the part I'd push back on. once engineers know a dashboard is surfacing their raw messages to a team lead, including the ones where they're venting at the model, people stop venting honestly and start writing for the audience instead - which quietly kills the exact signal you're trying to capture. token cost and skill usage feel like the genuinely useful team-level metrics here, the message-content angle feels like it's optimizing for a screenshot-worthy launch post more than for something a team actually wants turned on
Opaline
@galdayan fair, it’s a tradeoff. some people will write for the audience once they know a lead sees it. but the analysis feature looks for patterns across sessions, like where people get stuck or what the agent handles badly. the swearing highlight is there to surface the frictions engineers hit, beyond just where the agent screwed up and apologized. roll it up weekly and you learn how to use agents cheaper and better.
Dial
@evrendombak that pattern-across-sessions framing is the real product, honestly, the swearing highlight is just the hook that gets someone to open the dashboard. the thing i'd worry about is false positives, a session can look like "the agent handled it badly" when actually the task itself was just genuinely hard. how does the weekly rollup separate those two, or is that still mostly a human judgment call once you're looking at the flagged sessions?