Your team’s Claude Code,
working as one team
Approve a to-do and Claude Code takes it to a PR.
When it needs a call, a teammate jumps into the session.
Your backlog
doesn’t wait anymore.
From a one-line fix to a new feature, write it as a to-do. Agents on your team’s Macs take it to a pull request, within your developers’ rules.
Learn more about the agent database →Agent database
Insights
MinaExport does nothing on iPadEmpty
LeoLeo
Jayden
Jane
Awaiting approvalApprovedNot startedIn progressExport does nothing on iPad
AngieDefault the pricing toggle to yearlyLeo
ApprovedIn progressDefault the pricing toggle to yearlyJaneMatch button spacing to the new specJane
ApprovedIn progressMatch button spacing to the new spec
SamAdd a team invite step to onboardingJayden
ApprovedNeeds answerAdd a team invite step to onboarding
YunaShow yearly savings on the plan cardJayden
Awaiting approvalNot startedJaydenCrash on launch on iOS 17Jayden
ApprovedIn progressCrash on launch on iOS 17Export does nothing on iPad
MinaMina
Done, following the agent guide. Tests and type checks pass. I opened a PR.
Leo+12 −3 · 2 files
MergeMerging…MergedWith multiplayer AI,
staying in sync isn’t work.
Nothing to snapshot
Your teammates’ sessions sit in the sidebar, live.
Open one to see where they’re at.
No screenshots, no status pings.
Angie Angie1:58 PM
Retry the charge before we give up on the order.
Bottari1:59 PM
On it. Adding a retry loop in retry.ts.
✓Read checkout.ts · pg.ts
✓Edited retry.ts
✓Edited checkout.ts
Running pnpm test…
retry.tsAngie is editing
export async function retryCharge(order) {
const max = 3;
for (let i = 0; i < max; i++) {
const res = await pg.charge(order);
if (res.ok) return res;
}
return queueWebhookRetry(order);
}
Jane Jane2:02 PM
Does the plan picker still belong in sign-up?
Bottari2:03 PM
No. Most teams pick a plan after their first session.
Move it there, and sign-up stays at two steps: email, then workspace.
Signup.tsxJane is editing
export function Signup() {
const [step, setStep] = useState(1);
return (
<Form steps={2} onDone={goHome}>
{step === 1 && <Email />}
{step === 2 && <Workspace />}
</Form>
);
Leo Leo2:05 PM
Rewrite the pricing page for the three new tiers.
Bottari2:06 PM
Drafting. Reading the tier table first.
✓Read tiers.json · pricing.md
✓Edited pricing.md
Writing FAQ section…
pricing.mdLeo is editing
# Pricing
## Starter · free
One workspace, three seats.
Sessions stay for 30 days.
## Team · $12 / seat
Unlimited sessions and memory.
Nothing to re-explain
Stuck on an error? Mention your lead in the thread and they answer inside your session — same context, same line. No logs, captures, or long write-ups.
Leo Bottari2:32 PM
A: retry now, or B: add back-off?
JaneGrowth · Mac StudioJaydenEngineering lead · MacBook ProAngieProduct · MacBook ProLeo
Bottari2:32 PM
A: retry now, or B: add back-off?
@Jaydenneed your call on this.
Jayden2:34 PM
Makes total sense. Let’s go with Option B.
Nothing to copy
Mention a doc and Bottari edits the original your team is already in.
No copies, no links to send,
no “which version is this?”
Leo Leo3:02 PM
Jayden picked Option B. Let’s add the back-off.
Bottari3:03 PM
Got it. The spec still says the policy is to be decided. Want me to write it down?
Leo3:04 PM
Payment retry spec Update the retry cap to 3 and add back-off.
Bottari3:04 PM
Opening the spec. Jayden is already in it, I will edit the retry policy next to him.
Payment retry spec
Edited just now · Jayden and Bottari editing
Retries: retry the charge before showing the payment-failed screen.
Retry policy: to be decided
Failure screen: show the retry button after every attempt.
Nothing to dig through
Done with your part?
Hand the whole session to the next teammate.
They pick up with full context.
AngieLeo
HANDOVER TO…
LeoMac StudioJaydenMacBook ProJaneMacBook ProAngie2:12 PM
Where do new teams drop off in onboarding?
Bottari2:13 PM
Most stop at the plan picker. Only 62% reach invites.
✓Read funnel.csv · Signup.tsx
Angie2:19 PM
Mock up onboarding: sign-up, plan picker, invites.
Bottari2:20 PM
Invite screen is built. No backend yet.
Leo took over from Angie
Leo2:31 PM
All caught up. Starting on the invite API.
Bottari2:31 PM
Thinking…Invite screen sends email and role. Drafting the endpoint.
Multiplayer AI
for the Claude you already use
Bottari runs on your own Claude account. We add the team part.
Never used to train models. Team data stays in your workspace.
Connected
on your team's work.
A doc is a snapshot.
A session is the work
A doc hands over the past. A session puts your teammate inside the work, with you.
Sharing a doc
Sharing a session
A summary of what happened
What is happening, live
Whatever you remembered to write down
Everything: the whole thread, sources included
After reading, asking, and re-explaining
Immediately, from inside the session
A new thread they start from scratch
The same thread, with you
Your time, twice
None. It is the same session
Your team’s memory, in every session.
Meetings, product data, docs, chat. Bottari keeps all of it in one memory, so every session starts already knowing.
Meeting notes that don't evaporate
Turn on AI notes in a scrum call. Decisions land in the thread as you talk.
Product data, live
App Store, Play Store, GitHub, Analytics, Ads: connected once, synced always.
Docs the team shares
Specs and notes live next to the sessions that wrote them.
Team chat, in the room
Channels, threads, reactions, and Bottari is a member who remembers.
JaydenAngieJaneLeoAI notes
- Jayden Ship the pricing copy without the FAQ.
- Jayden Angie writes the release notes.
- Jane QA sweep moves to Thursday 3 PM.
- Angie Retry cap 3, then webhook retry. Agreed.
- Angie Jane takes the sign-up drop-off spec.
Onboarding revamp PRD
Edited just now · 3 editing
Users drop off at the third field of the sign-up form. GA4 shows 38% leave before the plan step, most of them on mobile.
Goal: cut that in half. Two steps instead of four.
Scope: sign-up form, plan picker, welcome screen.
Angie9:41
Standup notes are in the thread. Two open items.
Jayden9:52
Taking the checkout retry. PR by noon.
Leo10:02
Retry cap is merged. Staging looks clean.
👀2🎉1🚀3
Jane10:03
Nice. QA sweep starts at 3.
👍4
Jayden10:04
@Bottari what changed in retry.ts today?
Bottari10:04
Capped at 3, then webhook retry. Angie's call in turn 12.
Free through 2027
if you join in 2026
Everyone who joins by December 31, 2026.
Pro
$0$25per seat / month
Free through all of 2027 for everyone who joins by December 31, 2026.
- Shared live sessions
- Mentions and handovers
- Team context: meetings, data, docs
- Unlimited sessions
Enterprise
Custom
SSO, audit log, custom data policies and dedicated support.
Talk to us- SSO and admin controls
- Audit log
- Dedicated support
- Custom data policies
Frequently asked questions
Do I need Claude Code?
Yes. Agents run on Claude Code on your Mac, signed in with your own Claude account, and AI usage is billed to your Claude subscription. We don't resell or replace it, and other models are on the roadmap.
What platforms are supported?
Apple Silicon Macs (M1 or later) with Claude Code installed. Intel Macs and Windows aren't supported yet.
What can an agent do in my repository?
Only work on to-dos your team has approved. Each agent runs on its owner's Mac through Claude Code, in local copies of the repositories you picked. An admin picks the approval policy: Always PR only, PR only for risky changes (the default), or Always merge. Under any policy, changes to dependencies, migrations, CI, or config files wait for a person to review, and anything that can't be undone, like deleting data, is asked before it starts.
Where does my code go?
Your repositories stay on your Mac and on GitHub. The work happens on your Mac in Claude Code, and what it sends to the model follows your Claude plan's data policy. Bottari's servers keep what your team shares, like sessions, docs, and to-dos, including any code that shows up in them, so teammates can see the work. It's sent over TLS, stored on encrypted disks, and never used to train models.
Is my data used for training?
No. Bottari never trains models on your sessions, documents, or connected data. What you send to the LLM follows the data policy of the provider you signed up with, such as Anthropic for Claude.
How does the free offer work?
Join by December 31, 2026 and you stay free until December 31, 2027. It counts for every person who joins in time, whether you start a team or get invited to one.
When does billing start?
Everyone who joined in 2026 stays free through 2027. Anyone who joins from January 1, 2027 is a paid seat: Pro at $25 per person per month, Enterprise by contract. We'll tell you well in advance, and nothing is charged until you add a payment method.
Can I use it solo?
Yes, but that's not the point. Bottari is built for the moment you bring someone else into the session. Solo works; multiplayer is why it exists.
Can I keep a session private?
Yes. A session stays private until you share it. Then you pick what each person gets: view to read, comment to leave notes, or edit to prompt Bottari with you.
Which sources can I connect?
App Store, Play Store, GitHub, Google Analytics, and Google Ads at launch — so Bottari can read your releases, code, traffic, and ad performance without anyone pasting reports in. More sources ship through the beta.