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?
would love to hear from you.
best, evren
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.
On the analytics side, Opaline competes within Analytics, Developer Tools and Artificial Intelligence — topics that collectively have 1.2M followers on Product Hunt. The dashboard above tracks how Opaline performed against the three products that launched closest to it on the same day.
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.
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