Opaline - PostHog for team Claude Code and Codex sessions.
by•
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.
Replies
hi product hunt! evren here, builder of opaline.
we’re building team-wide, message-level analytics for your claude code and codex sessions:
a way to pull back the curtain on how your team actually codes with agents.
why? the tools people reach for today, like ccusage or /insights inside claude code, are single-user, single-model, and pretty shallow. they’ll tell you how many tokens you burned and what it cost, maybe a high-level insight or two. that’s fine for a solo dev. but real teams rack up thousands of sessions across dozens of repos and models, and right now there’s just no good way to see any of it together.
we want to change that. understanding how your team works with coding agents should be effortless.
like you’d never run a website without analytics... it's obvious that you need them for your agentic coding sessions too.
what’s our backstory? we first built opaline for our own team at obsessiondb (yc f26) as a little side project called “rudel,” and now i’m here to give it a proper life. we were all deep in cc and codex every day, but nobody could see how anyone else was working.
when someone struggled with a skill, it stayed on their machine.
when someone got stuck, it stayed on their machine.
when claude told "you're absolutely right!" for the third time it stayed on their machine.
(if the machine wasn't punched into already)
the usage dashboards out there only showed us our own numbers, and none of them kept the history we needed to actually learn over time.
so we built the thing we wished existed: a shared place to see, replay, and learn from our sessions.
how is your team using coding agents today? what can’t you see that you wish you could?
would love to hear from you.
best,
evren
Curious how you handle sensitive stuff in the sessions though Coding sessions can have a lot of things you probably don’t want sitting in a team dashboard.
@sheikh_umair1 great point, we're filtering known secrets for everyone and for teams with high security standards we offer on-prem / self-hosted deployments where all the data stay in your cloud. and you can choose what to upload so you don't upload your personal sessions to the team dashboard.
I would love to learn how many of our sessions are actually producing something good, something actually valuable. What are some ideas for measuring this?
@escobarjose it's definitely easier to track agent runs that went wrong. we're still exploring what we could do. one thing we've done already is tracking positive replies by the user and another idea we're working on is correlating green merged PRs
I could see this being handy for teams trying to figure out where they’re actually spending time with Claude/Codex.
@sukumar_sukumar1 yes, changes like every 4 weeks haha. and just changed yesterday with opus 5.5 vs sol 6
So the goal of this is for the team to get better over time by learning exactly how they message and the results of it? Pretty cool
@lucas_duys yes sir! 🫡
Great stuff, even though I fear I'll need to change the way I talk to my agents if this is exposed haha
@wherelambo the more you swear when you're pissed off the more data you have to steer your agents ;)
Dude this i literally EXACTLY what i needed.
@jaye_temenu appreciate it!
Finally! We're duplicating so much with no way to figure out what's been solved already
@heychristoph thanks christoph!
Tested it and actually gave me some interesting insights
@lukas_bormann nice thanks man!
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?
@wwenioaguiar great take. actually working on it as we speak :)