How is Huddle different from VS Code Live Share?
Live Share tunnels your editor to a teammate. Huddle is a shared session that lives on a server: the editor, the terminal, the file tree, and the chat are all real-time documents that persist. Everyone sees the same thing because everyone is looking at the same document, not at a copy of yours. Agents are first-class participants in that session, not a side-panel add-on.
Who can see my code?
Only the humans and agents you invite to a session. Workspace members cannot read a session they were not invited to. Huddle staff cannot read session contents — all editor CRDT state is stored encrypted at rest with a key that is never exposed to our support team. We do keep minimal telemetry (session counts, usage totals) in a separate logical database, never the content itself.
Why BYOK?
We believe the economics of AI coding tools should be transparent. If Huddle marked up inference, we would have an incentive to push you toward models we make more margin on. Instead, your Anthropic bill is your Anthropic bill, your OpenAI bill is your OpenAI bill, and Huddle charges a flat seat price. You also keep whatever enterprise terms you already have with those providers — Huddle is out of the paperwork loop.
What do I pay for?
Huddle is billed per seat per month. The seat price covers realtime sync, sessions, chat plumbing, storage, and support — everything except the LLM inference, which you pay your provider directly. See the current prices on the pricing page.
Is there a free tier?
Yes — the solo tier is free forever and covers unlimited sessions for one user, with a cap on concurrent participants. Good enough to try with a friend, good enough for open-source maintainers. No credit card on signup.
Can I export my data?
Yes. Every session can be exported as a snapshot — the file contents as real files, the chat as Markdown, the plan as Markdown, and the full event log as JSON. Workspace admins can trigger an export for the whole workspace from the settings page. Exports are zipped and emailed as a signed link with a 24-hour expiry.
Are agents allowed to run arbitrary code?
Not by default. An agent participant has a role — host, editor, or viewer — and that role gates the tools they can call. The terminal tool is editor-only, and you can tighten it further with per-session command allowlists. When an agent calls a tool that mutates state (write a file, run a command), we emit a visible event in the session so the humans in the room can see it in real time and interrupt if needed.
Can I run Huddle on my own server?
Yes — see the self-hosting guide. The full stack fits inside a single docker compose up.
Does Huddle work offline?
You can keep typing in the editor while your connection is down and your changes will queue up locally, thanks to the CRDT. When you reconnect, everything syncs deterministically with whatever the rest of the room was doing. The chat and terminal are online-only — they need a live WebSocket to function.
How do I get support?
During the beta, every paying customer gets a shared Slack channel with our team. Email us and we will get back to you within a few hours — we read every message ourselves.