Opaline

Opaline gives engineering teams a shared workspace to understand what their AI coding agents are actually doing. Built by Opaline Labs, Inc., it connects to Claude Code and Codex sessions via an open-source MIT-licensed CLI, then surfaces session traces, API costs, token volumes, and agent activity in a web dashboard. The CLI is available on npm and requires Node.js 20 or newer.

What It Is

Opaline is a session analytics and observability platform for teams adopting AI coding agents. It sits between your local Claude Code or Codex sessions and a shared team dashboard, uploading full session transcripts — prompts, responses, tool calls, commands, and subagent activity — so engineering leads can see where effort went, what patterns recur, and where agents struggled. The core CLI is open source under MIT; the web app and advanced analytics features are a commercial SaaS product.

How the CLI Works

The npx opaline@latest command discovers local Claude Code and Codex sessions grouped by repository, lets you toggle which repos sync, and then sets up hooks for automatic future uploads. Key behaviors:

• Sessions already uploaded to the destination are skipped on re-run.
• Turning a repository OFF stops future uploads but does not delete previously uploaded sessions.
• Known secret patterns are filtered before upload, though the project's own docs note filtering cannot guarantee every secret is removed.
• The CLI also sends limited usage analytics (version, OS, setup results, session counts) that exclude transcript content and local paths.

Common commands include whoami (account and upload failures), doctor (auth, connection, and hook checks), and update (manage persistent installations).

What the Dashboard Shows

The Opaline web app organizes session data into several views: a Dashboard with API cost trends, per-member and per-repository breakdowns, and model usage; a Sessions view with deep trace timelines; a Skills view for recurring patterns; and a Repos and Team view for organizational context. The demo on the homepage shows daily API cost charts, member-level spend percentages, and model-level cost splits.

Lineage: Formerly Rudel

Opaline was previously known as Rudel. The GitHub repository (opalinehq/cli) notes it is "Formerly rudel," and the CLI docs include a migration guide from Rudel. The project appeared on Product Hunt (ranked #5 on a May 2026 launch) and on Hacker News (144 points, 86 comments on a Show HN post by keks0r), indicating early community traction under the Rudel name before the rebrand.

Update: opaline-cli v0.10.0

The latest release is opaline-cli@0.10.0, published September 18, 2026. The repository was last pushed September 21, 2026, and last updated September 25, 2026, showing active development. The project has 303 stars and 15 forks on GitHub as of the latest metadata.

Deployment Model and Privacy Tradeoffs

Opaline's standard deployment is cloud-hosted SaaS. Enterprise plans add on-premises and self-hosted deployment options, SAML/SCIM, granular admin controls, invoice/PO billing, and dedicated account management. Because the CLI uploads full session transcripts including source code and tool output, the project's own documentation advises enabling only repositories whose session data you are permitted to share with Opaline.