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.
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.
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.
tracking every you're absolutely right moment per session is kinda genius, usefull for eng leads 😂
Report
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?
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.
@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
Report
@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.
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 🫡
Does this support Claude Chat / Cowork ?
Opaline
@jay_janarthanan1 no it doesn't just yet but it's in the backlog!
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.