Connect your AI once
Sign in with Google. No API key, nothing to install.
Plan in Claude. Build in Codex. Approve in ChatGPT. One shared record for all of it.
Free during early access. Google sign-in, no API key.
Maya plans in Claude, Ryan builds with Codex, Priya reviews in ChatGPT. None of those chats know about each other, so people carry everything in between.
Each person connects the AI they already use, once. Every chat after that starts from the same record and writes back to it.
Sign in with Google. No API key, nothing to install.
Your tasks, and what’s waiting on you, before you type a word.
Picking it up means no one doubles up. Progress and drafts follow.
Legal in ChatGPT tomorrow, or voice on the drive in. The history is intact.
Works in Claude, ChatGPT, Codex and Claude Code.
One record for your team. Every AI you use reads and writes it.
CLA-212 Onboarding email flow moves through Brief, Review, Legal and Approval. Claude, working for Maya, revises the draft from Priya's legal comment and leaves it in review. Only a person can move it to Done: Sam approves it.
A versioned brief page. Priya from Legal comments on line 2: we can't say guaranteed. Claude, working for Maya, revises the line from her comment and saves version 4.
AI work log for CLA-212: Claude, working for Maya, picks up the task so no one doubles up, shows it is still active while it works, reads the brief and its 3 key messages, writes 3 versions of the welcome email, and leaves them waiting on Maya.
CLA-212 moves from Maya in Claude to Sam in ChatGPT, carrying brief v4, the 3 email drafts and the AI work log. Sam asks ChatGPT what is waiting on him and gets the task with its history. No chat transcript is passed along.
The attention queue shows four items waiting on Sam when his next chat starts: a review of CLA-212, a legal comment from Priya on CLA-208, stale work on CLA-203, and a decision on CLA-215 from Jordan's team.
Time on CLA-212, 6 hours 50 minutes in total. People: Maya 1 hour 10 minutes, Priya 30 minutes, Sam 20 minutes. AI: Claude 1 hour 30 minutes, Codex 3 hours 20 minutes.
The next step doesn't have to be yours, or in your tool.
Plan by voice in Claude on the drive in. Open CLA-212 in ChatGPT at your desk.
Ryan's Codex picks up the task with the brief and key messages attached.
Legal comments on the exact line. Clients comment from a link, no account needed.
CLA-212
Onboarding email flow
Done
Created the task. Saved the brief and three key messages.
Brief3 key messages
Picked up the task. Built the templates, moved to review.
Picked up3 commitsMR !77
“We can't say ‘guaranteed’.” The AI revised the line from her comment.
Line commentRevised
Read the revised draft. Approved and moved it to Done.
Approved
Read the brief from a shared link. Left two comments, no account needed.
Shared link2 comments
Your team already works in Claude, ChatGPT and Codex, so Clarabit meets them there. The web app is for what chat is bad at: reading a whole page, commenting on one line, approving.
01
Pick up, update, comment or flag a blocker without leaving Claude, ChatGPT or Codex. Links land on the exact item.
Pick up CLA-212, the onboarding email.
Onboarding email flow
It's yours. Jordan left two comments on the copy, so I'll start there.
Open CLA-212 in Clarabit02
Inference runs in the tools you already pay for. Clarabit is the shared memory and coordination layer, and it gets better as they do.
Your tools do the thinking
No model inside
03
Every action is logged under its own name, separate from people's edits, and fails exactly where that person would.
Maya picked up the task
Claude (Maya) read the brief
Claude (Maya) drafted email v3
Claude (Maya) tried to approve v3
Not allowed Same check as the web app.
Maya asked Sam to approve
Person AI, acting for its person
Useful on day one for one person. Better when the whole team is on it.
I built Clarabit because I needed this workflow and couldn't find another tool that let me work this way. I don't want it to replace Codex, Claude, or whichever tool is better six months from now. I want it to keep the work coherent while those tools change.
Clarabit is the platform Limeade Labs runs on. Client work, product work and the newsletter all go through it, from Claude, Codex and ChatGPT.
The thinking behind Clarabit, as it happened, on Ryan's newsletter.
An occasional email when something changes: new hosts, directory listings, what shipped. No account needed.
We're looking for people who'll tell us where it falls apart on their work, not people who'll admire a demo.
PriyaLegal, on line 2
We can't say “guaranteed”.