Bring your team
into the session
One shared room where your team and AI share live context.
No silos. Nothing to re-explain.
4 things that disappear
Nothing to post
Your teammates’ sessions sit in the sidebar, live. Open one and see exactly which files their AI is touching — and steer yours around them before the PRs collide.
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 Leo2:28 PM
Starting on the checkout retry. Cap is 3 attempts, then we show the payment-failed screen with a retry button.
Bottari2:29 PM
Got it. Editing retry.ts and checkout.ts. I will wrap the PG call in a retry loop with a 3-attempt cap and a short back-off between tries.
Leo2:31 PM
Retry change is in. Running checkout again on the staging card to see if the second attempt goes through.
Bottari2:32 PM
Ran it. The first charge fails as expected, but the second retry fails too. PG returns 402 both times.
Leo2:33 PM
@Jayden ParkCan you take a look?
Jane KimGrowth · Mac StudioJayden ParkEngineering lead · MacBook ProAngieProduct · MacBook Pro
Jayden Park joined the session
Nothing to copy
Mention a doc in your session and Bottari edits the original: the one your team is already in. No copies, no links to send, no “which version is this?”
Leo Leo3:02 PM
Second retry still fails with 402. We need a back-off, not just a cap.
Bottari3:03 PM
Agreed. 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: when the PG returns 402, 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 summarize
Taking the afternoon off? Reassign the live session instead of writing a doc. Your lead asks Bottari why a decision was made — and keeps the work moving.
Jane Kim＋Manual↑Angie
Jane Kim
HANDOVER TO…
Jane KimMac StudioJayden ParkMacBook ProLeoMacBook ProAngie2:19 PM
Retry cap is in. Checkout passes on staging.
Bottari2:20 PM
Confirmed. Two PG errors left on the second retry.
Handed over to Jane Kim
Jane Kim2:31 PM
Let’s pick up from here.
Bottari2:31 PM
Thinking…Here’s where we are: sign-up is down to two steps, and the plan picker moved after the first session. Angie flagged a 38% drop before the plan step.
A team layer 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
The context your team keeps losing,
collected and used
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.
Jayden Park9:52
Taking the checkout retry. PR by noon.
Leo10:02
Retry cap is merged. Staging looks clean.
👀2🎉1🚀3
Jane Kim10:03
Nice. QA sweep starts at 3.
👍4
Jayden Park10: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
Every seat you fill by December 31, 2026.
Pro
$0$25per seat / month
Free through all of 2027 for teams that join in 2026 and seats filled by December 31.
- 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 a Claude subscription?
Yes. Bottari connects to the Claude account you already have. We don't resell or replace it.
Is this a new AI model?
No. Bottari is a workspace layer. The AI is your Claude — same models, same limits.
What platforms are supported?
macOS 14 or later for the beta. Windows and Linux are on the roadmap.
How does the free offer work?
Create a team between October 14 and December 31, 2026 and it stays free until December 31, 2027. Everyone who joins that team by December 31, 2026 is free too.
When does billing start?
Early-access teams stay free through 2027. Starting January 1, 2027, new teams and teammates added after December 31, 2026 are paid seats: Pro at $25 per seat per month, Enterprise by contract. We'll tell you well in advance, and nothing is charged until you add a payment method.
Is my data used for training?
No. Your sessions, documents, and connected data are never used to train models.
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.
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.
Stop handing off. Start building together
FREE THROUGH 2027 for every team that joins in 2026. $0 for every seat filled by December 31. if you join in 2026
Learn more →Get the link
the moment we open
One email on October 14. No newsletter.
You're on the list
The download link lands in your inbox on October 14.
We announce first on X and Product Hunt.