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.
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?
Evren — the “PostHog for Claude Code” framing lands. The gap I keep hitting on tools like this is the first shared insight: before npx and upload choices, a new lead needs one teammate session that makes the team dashboard feel inevitable.
Congrats on the launch.
tracking every you're absolutely right moment per session is kinda genius, usefull for eng leads 😂
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.
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
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.
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?
I build analytics myself and the setup looks really smooth. One question: How do you handle model updates? A lot of these numbers probably change with every new model, so comparing this month to last month might just show the new model instead of the team getting better. Is it possible to split the metrics by model version?
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.
I could see this being handy for teams trying to figure out where they’re actually spending time with Claude/Codex.
This is kinda the part that stood out to me So much of what happens in these sessions just stays on someone’s machine.
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.
Finally! We're duplicating so much with no way to figure out what's been solved already
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?
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.
Great stuff, even though I fear I'll need to change the way I talk to my agents if this is exposed haha
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
About Opaline on Product Hunt
“PostHog for team Claude Code and Codex sessions.”
Opaline launched on Product Hunt on September 24th, 2026 and earned 147 upvotes and 39 comments, placing #8 on the daily leaderboard. 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.
Opaline was featured in Analytics (173.9k followers), Developer Tools (520.4k followers) and Artificial Intelligence (479.9k followers) on Product Hunt. Together, these topics include over 228k products, making this a competitive space to launch in.
Who hunted Opaline?
Opaline was hunted by evren. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Opaline stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
evren
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