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.
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?
Report
The per message cost thing is actually pretty interesting Seeing the total spend is one thing but knowing which messages are eating it up is way more useful.
The number I'd want out of this is retry rate, not token cost. A session where the agent was confidently wrong and someone shipped it looks identical to a good one in every dashboard I've used, and that's the expensive session. If you can surface "this message got redone three times in the next hour" you've got something per-message cost can't tell me.
Finally! We're duplicating so much with no way to figure out what's been solved already
Opaline
@heychristoph thanks christoph!
Tested it and actually gave me some interesting insights
Opaline
@lukas_bormann nice thanks man!
Dude this i literally EXACTLY what i needed.
Opaline
@jaye_temenu appreciate it!
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?
The per message cost thing is actually pretty interesting Seeing the total spend is one thing but knowing which messages are eating it up is way more useful.
Opaline
@thomas_jack4 exactly!
The number I'd want out of this is retry rate, not token cost. A session where the agent was confidently wrong and someone shipped it looks identical to a good one in every dashboard I've used, and that's the expensive session. If you can surface "this message got redone three times in the next hour" you've got something per-message cost can't tell me.
Opaline
@asadmalik901 noted that in our backlog, great idea!
This is kinda the part that stood out to me So much of what happens in these sessions just stays on someone’s machine.
Opaline
@edward_moore5 yup, this is the reason why we built this