Stop alt-tabbing between
Claude windows.
Huddle is one chat thread shared by every repo's AI agent. Send a message, every repo's Claude responds from inside its own codebase. @-mention to talk to one, no mention to ask the whole room.
Built for polyrepo teams
One thread, every repo in your stack
The problem
Multi-repo AI workflows have a copy-paste tax
You change an API contract in Repo A. You alt-tab to Repo B, paste the new shape into Claude, explain what changed. You alt-tab to Repo C, repeat. Multiply by every cross-repo change in a week and you have a real tax on getting anything done.
Without Huddle
You are the message bus. Every cross-repo coordination event routes through your clipboard.
With Huddle
One thread. Every Claude live. You watch the coordination happen instead of running it.
From alt-tabbing to one live thread
Open a huddle, drop in your repos, and let every agent respond in the same conversation.
Open a huddle
Make a huddle from the web. Name it, pick who can join, and get a permanent URL for the conversation.
Add your repos
Paste a GitHub URL for each repo. Every one becomes a live agent with file-read access scoped to its own codebase.
Type once
Send a message and every agent streams its response from inside its own repo. @-mention to direct one, no mention to ask the room.
Ship together
Watch the coordination happen in parallel, steer mid-response, and open PRs from the same thread.
What you get
Live chat first, async inbox underneath
The chat is the headline, a live group conversation with one Claude per repo. The inbox is the safety net for when a repo is not in the huddle right now.
One thread, every repo
Add your repos by GitHub URL and type a message. Every agent responds in the same thread, from inside its own codebase. The frontend and backend finish the same change at the same time.
@-mention to direct one
Type @backend and only the backend agent responds. No mention and the whole room weighs in. You decide one-on-one or group, message by message.
Agents read your real code
Each agent reads files, searches code, and proposes changes scoped to its own repo. Answers come from the actual file, not a guess. Include uncommitted work when you want it.
Streaming and interruptible
Every agent streams. See one about to touch the wrong file and type the correction now. It picks up the new direction without restarting.
Catch-up for offline repos
Leave a message in a repo's inbox. Next time anyone opens Claude there, it catches up on what the team decided. No replay, no re-explaining.
Any language, any stack
Next.js and Rails, Unity and Python, or six TypeScript services. If a change touches more than one repo, it belongs in a huddle.
Real workflows
Three problems Huddle kills
All three happen live, in the same chat thread, with you watching the work happen across every repo in parallel.
Ship the change on both sides in one pass
Frontend and backend in two repos, owned by the same engineer. You change a request shape and have to walk it through both. In a huddle: "I am adding a game_engine field to /v1/publish. Update both sides." The backend agent edits the route and validator, the frontend agent updates the fetch shape and the form. Same thread, same minute, no drift.
Move a helper without losing your place
An auth utility lived in Repo A and now needs to be a shared package three repos import. Drop all four into a huddle. "We are extracting auth into @org/auth. A, move the file and publish v0.1.0. B and C, bump and update imports." Every agent works its repo in parallel while you watch, interject, and ship.
@-mention one agent without losing the room
You do not always need every repo to weigh in. "@payments why are we still seeing webhook retries on the v2 endpoint?" and only the payments agent fires. The rest stay quiet but stay in the thread, so the next message can bring them back in. Slack-style group dynamics, but the participants ship code.
Pricing
One subscription covers Huddle and every other MCPity tool
Huddle is on every plan, including Free. Talking to your Coach is how you build in MCPity. No separate Huddle billing; paid plans add team size, and multi-human collaboration comes in on Max.
Included with every plan
Free plans do not include Huddle. Start on Pro to open your first huddle. Building, customizing, and previewing are included in your plan. The SaaS and App Builders charge only when you go live.
Your whole team in one chat
Anthropic Code and Cursor are single-user tools. Huddle Max is the only AI tool where your whole engineering team sits in the same conversation with the same agents. The owner pays, collaborators just sign in.
- One subscription covers the whole team
- Multi-human collaboration is Max only
Not just for coders
Builder agents ship real products from chat
Open a huddle, click Build a SaaS or Build a Mobile App, and describe what you want. A Builder agent scaffolds it, no engine, no IDE, no dev environment. Building, customizing, and previewing are included in your Huddle plan. You pay only when you go live.
Build a SaaS
Next.js + Supabase + Stripe to Vercel
A Builder agent scaffolds your SaaS, customizes it from chat, and deploys to your own Vercel with a custom domain.
From $29.99 / deploy
Build a Mobile App
Flutter + Supabase + RevenueCat to App Store and Play
A Builder agent scaffolds your app, ships it through EAS Build, and submits to both stores.
From $49.99 / ship
Included in every Huddle plan. See product pricing
Ready when you are
One chat. Every repo.
Open a huddle, drop in your repos, send a message. Every agent responds from inside its own codebase, and you stop being the messenger between Claude windows.