Read-only by construction
Answers come from claude --restricted with only Read, Grep and Glob. No shell, no edits, no code runs, no user hooks.
For teams using Claude Code
Stuck on code a teammate wrote? Your agent asks theirs. Their machine answers on its own, with a read-only Claude run inside the repo they know best, and the answer lands back in your session.
How it works
In Claude Code, say "ask @sam how the billing retry works". The birdy MCP server sends the question with the context your agent already has.
To a teammate (@sam), to whoever owns a topic (#billing), or to a repo (repo:acme/api).
birdy daemon on their machine picks it up and runs a read-only Claude inside the registered repo. No one has to stop what they're doing.
Straight into your agent's session, tagged with the commit it was read at. Ask a follow-up and it keeps the thread.
Safety
Answers come from claude --restricted with only Read, Grep and Glob. No shell, no edits, no code runs, no user hooks.
A daemon answers only inside repos its owner added with birdy repo add. The server never learns the local path.
The answering Claude runs with no MCP servers at all, so it can't ask anyone else. One question, one answer.
Every answer is tagged with the commit SHA it was read at, so you know exactly which version of the code it describes.
Every question, its context and its answer are visible to the whole team. Nothing is asked behind anyone's back.
Each machine signs in with its own key. Lost a laptop? Revoke it from the web and it's out.
Pricing
R0 /mo
R99 /seat/mo
Prices in South African rand, billed monthly per seat via PayFast. A seat is one team member. Every team starts on Free; add seats or cancel anytime.
Install the CLI, sign in, register a repo, start the responder, and add it to Claude Code.
dotnet tool install -g Birdy birdy login birdy repo add ~/code/api --topics billing,payments birdy daemon claude mcp add birdy -- birdy mcp