Your AI coding is a black box. Oh turns it into a mirror.
After every Claude Code and Codex session, Oh shows you where your time and tokens went — and quotes your own words back at the moment they cost you: "that 'ok i think it worked' cost 418k tokens — the agent re-read the whole thread just to hear it." There's no separate AI reading your code — Oh surfaces the evidence and your own agent (the Claude or Codex you already run) does the talking, over a verbatim record of every session. Your week to see · Yours to recall · Your team's to ask.
On a team where AI writes most of the code, the bottleneck isn't writing — it's re-explaining. Someone ships a PR, and everyone else has to interrupt them: "wait, why does this work this way?" The answer existed, in full, in the author's AI session. Then the session ended.
"We chose the queue because retries were poisoning the batch and the vendor limit meant we…
— gone. Unless something remembers.
Time anatomy (you prompting vs. the agent working vs. you away), token economy, rabbit-hole detection — plus tips that quote your own words back at the moment they cost you. Useful solo, from day one.
Every past session — across Claude Code and Codex — is memory your agent can pull from. Last month's plan, last week's fix, the thing you almost remember deciding. Useful solo, from day one.
Your agent queries your teammates' reasoning and answers with citations — instead of you interrupting the author to re-explain. Cross-tool: Codex answers from a Claude session, and vice versa.
Every time a turn ends in Claude Code or Codex, a detached process reads what's new in the session file. It never blocks your typing.
Prompts, explanations, and one-line action summaries are embedded into the team brain. File dumps and raw output are dropped; secrets are masked before anything leaves your machine.
Any teammate's agent asks in natural language and gets ranked, cited excerpts — recency-boosted, so the current decision wins when plans changed.
Three ways to run Oh — all free during the beta, all the same CLI and the same capture. They differ in one thing: where your memory lives. Pick the row that fits.
We run it — bring nothing. The full product, including the shared team brain your teammates can ask. The fastest start, and the right call for teams.
Nothing leaves your machine. On-device store under ~/.oh/local, embeddings in-process — no account, no Supabase, no OpenAI key, no egress to allow-list. You get Recall + Insights; the shared team brain is the one thing it skips. The easiest version for a security-locked org to approve — works air-gapped.
Your own cloud. The full product — including the shared team brain — running in your Supabase with your OpenAI key. Free forever; the Elastic License keeps this path open.
Whichever you pick: restart Claude Code and Codex, then try it — "ask what I was working on last week". On hosted or self-host, teammates join with your invite code. Stuck? email us, a human answers.
Rather not run commands yourself? Each option above has a copy a setup prompt button — paste it into your agent (Claude Code, Codex, whatever you drive) and it does the install end to end.
During the open beta everything is free — hosted, no keys, no card. Paid tiers arrive when the beta ends. The cap will be memory, not features — everything works on Free and ages out after 30 days. The day an answer you needed has expired, you'll know exactly what you're paying for. Self-hosting stays free forever.
Six months from now, someone will look at your code and ask why.
Oh will know.