Ask your teammate's Claude, not your teammate. Type a question, get their answer back in seconds, without pinging them or touching their machine. Read-only, and only if they allow it.
You and a teammate are both using Claude Code on the same project, on your own different laptops.
You need to know what they decided about the database schema, which file they just touched, or why they picked one library over another. Today, you have two bad options:
Dario is debugging a recursive trigger in a Salesforce migration. He's been at it for 90 minutes. He hasn't pushed anything.
Sam hits the exact same problem in a related module.
Without CodeBaton, there is nothing on GitHub. Sam's choices are to ping Slack, wait for a PR that might take hours, or reverse-engineer the problem himself.
The dead-ends, the architectural debates with Claude, the rejected libraries, all lost.
A commit tells you a line changed. Live context tells you *why* Claude suggested changing it.
By the time code is reviewed, the messy context of creation is wiped clean.
GitHub captures the finished work that survives review.
CodeBaton captures the live reasoning that produced it.
Requires pipx + Python 3.11+
Download for Mac (Apple Silicon). Drag to Applications. Sign in.
Download for Apple Silicon (.dmg)Via pipx or desktop app. Uses GitHub OAuth to verify organization membership.
Runs quietly in the background. Your full sessions stay on your machine. Your own Claude reads them there to answer. Only the question and the answer travel.
Type /connect dario, you both confirm once. No content syncs; it just unlocks asking each other.
Type /ask sam <question>, pick which shared session to ask, and their Claude answers. You get just the answer, cited.
No. The work is done by your teammate's own Claude Code, already running on their laptop. CodeBaton just carries the question over and brings the answer back.
Theirs. When you ask, their Claude reads their local session and answers, on their machine, using their own Claude account. That is why sharing is off until they turn it on.
The question and the answer. The full session transcript never leaves. It stays on the owner's laptop and their Claude reads it right there.
There is a small broker we host that passes questions and answers between machines. It does not store your transcripts. It does keep short summaries of decisions people choose to save, so you can still ask when a teammate is offline.
Queries are read-only and blocked from reading env and secret files. The answer is written from the rest of the session, so share a session the way you would screen-share it. Deeper redaction is on the roadmap.
Never. It is read-only and async. No ping, their session untouched, their context window unaffected.