One brain per repo.
Every agent on the team reads from and writes to one memory for each repo. Decisions, the why, rejected approaches, conventions. What one person's agent learns at 11, everyone's agent knows at 2.
Your whole team's agents share one brain.
When Priya's Codex decides how the billing service handles retries, Marcus's Claude knows it by the time he opens the repo. A new hire's agent knows every decision the team ever made on day one. Repo-level memory, per-repo permissions, and an admin view of what ran unattended and who approved what. Everything else in Solo, for five people.
Same proof, same guarantee. Card is not charged until it proves it remembers. Reply "goldfish" for a full refund, any time in 60 days.
Admintweetycorp · 5 seats
liveLast night, unattended
billing-apiclaude · Priya's minidone
docs-sitecodex · Marcus's MacBookdone
billing-apiclaude · Priya's miniwaiting
Approvals
11:22 PMMarcus tapped yes on drop legacy_invoicesbilling-api
Memory today
billing-apiretry policy settled, and whyclaude · Priya
billing-apiidempotency key bug foundcodex · Marcus
Five people. Ten agents. Zero shared state.
Everyone on the team runs Claude Code, Codex, or both. Every agent starts every session knowing nothing about what any other agent decided. Priya's Codex settles the retry policy on Tuesday. Marcus's Claude proposes a different one on Wednesday. Codex flags Marcus's PR for the thing Priya already decided. The "why" lives in a Slack thread nobody can find, a DECISIONS.md nobody updates, and Priya's head.
Multiply Groundhog Day by the headcount. Then add the new hire, whose agent knows even less than they do.
What Team adds.
Per-repo permissions.
What runs unattended and what waits for a tap, set once per repo, applied to everyone's agents. The billing repo waits on everything that touches money. The docs repo runs free.
Admin view.
What ran unattended last night, on which repo, from whose machine. Who tapped yes on what. What got written to memory today, by which agent, for which person.
Your own storage.
Pin the team's memory to a bucket you control. Export all of it as markdown any time.
Everything in Solo, five times.
Two Macs each. Both agents. Phone thread. Files back. Browser hands. Schedules. Night Shift pack.
A Tuesday on a team of five.
Priya's Codex settles how the billing service handles retries: exponential backoff, cap at five, dead-letter after. It writes the decision and the why.
Marcus opens the billing repo. His Claude already knows the retry policy. It does not propose a different one.
Marcus asks Codex to review Claude's PR. Codex does not flag the retry code. It finds a real bug in the idempotency key instead.
Dev, hired Monday, asks his agent why the retries cap at five. It tells him. Priya was in a meeting.
Marcus's overnight run hits a prompt to touch the billing table. The billing repo policy says money waits. His phone buzzes. He taps yes. It is in the admin view by morning.
Standup. Nobody says "who decided this."
Day one.
A new hire's agent knows every decision the team ever made, and why, the moment they pair their phone. Not a wiki they will read later. Not a CLAUDE.md that stopped being true in March. The living memory of the repo, in the agent they are about to ask.
You can see what ran while nobody was watching.
Every unattended run, per repo, per machine, with what it did and what it opened. Every permission prompt, and who tapped yes. Every memory entry written today, with the agent and the person behind it.
Revoke a paired device from here. Change a repo's policy from here.
Team.
$149 a month for five seats.
$25 a seat after. Or $1,490 a year.
Everything in Solo, for five people, and one brain per repo. Per-repo permissions. Admin view. Pin memory to your own storage.
Start with fiveCard is not charged until it proves it remembers. 60 days, reply "goldfish" for a full refund.
Questions about teams.
Who sees what?
Everyone on a repo shares that repo's memory. Personal threads stay personal. The admin sees runs, approvals, and memory entries per repo; the admin does not see anyone's thread.
Can I keep some repos out?
Yes. Memory and permissions are per repo. A repo you do not add to the team stays on your Solo memory.
Where does the team's memory live?
Encrypted, keyed to the team, in Tweety Bird's storage by default. Or pin it to a bucket you control. Export all of it as markdown any time. Delete it with one command.
What about SSO?
Not at launch. Founders vote on the order; it is on the list.
What happens when someone leaves?
Remove the seat. Their paired devices are revoked. What their agents wrote to the repo memory stays with the repo, the way their commits do.
Can I try it with one person first?
Yes. Install Solo, run the proof, then add four seats from the thread when you are ready. The memory carries over.
Start with five.
One command per machine. Five minutes each. Tell Claude one decision, ask Codex on someone else's Mac, and watch it answer. Nobody's card is touched until it does.
Start with five$149 a month for five, $25 a seat after. Reply "goldfish" for a full refund, any time in 60 days.
Your laptop closes at 6. Your agents don't.