relai — see what your AI coding actually costs
One local dashboard for Claude Code, Codex, and opencode.
The problem
Developers are using more than one AI coding tool — Claude Code for one task, Codex for another, opencode for a third. Every tool keeps its own private record of what happened. When a team tries to answer basic questions — what did we build with AI this month? on which projects? was it worth it? — the data lives in three different places and nobody has a clean answer.
Telemetry reports end up blending real product work with weekend experiments. Signal gets lost inside the noise.
What relai does
relai reads the session files your AI tools already leave on disk and gives you one unified view. Every session, every project, every token — across Claude Code, Codex, and opencode, in one place.
Separate real work from experiments
One click — Auto-classify prototypes — and relai flags throwaway sessions automatically. Export telemetry for only the work that actually shipped. Finance sees accurate numbers, engineers keep their experiments private.
Move context between tools
Prototype in a cheaper local model, then hand the session to Claude with one click. relai summarizes the transcript, collects your memory files, and launches the next tool already knowing where you left off. Any source, any target.
Privacy by default
Everything runs on your laptop. relai opens your tools' data read-only and never writes back. Nothing leaves the machine unless you click Export. That makes it usable in regulated environments where sending transcripts to a SaaS dashboard isn't an option.
Why now
AI coding tools are proliferating faster than the tooling to measure them. Engineering leaders pay enterprise seats per developer with no way to see how much is actually being produced, on what, and at what cost. relai answers those questions from data teams already have — no integration, no vendor lock-in, no data leaving the laptop.
Download
relai ships as a standalone macOS app. No Python, no Terminal, no setup — drag it into Applications and launch.
Source on GitHub. Feedback, ideas, and partnerships welcome — reach out.