Frequently asked questions

MobSession turns a single Claude Code session into a shared room. One person runs the agent, teammates watch and steer in real time, and every turn shows who asked for it and what it cost. When something is still early access, we say so.

What is MobSession?

Mob programming for Claude Code. The host runs an agent on their own machine, shares a link, and teammates join to watch it work and queue prompts. Output streams live to everyone, and each turn shows who asked for it, how long it took, and what it cost.

Do I need an account to start?

No. Start a session and invite teammates without signing up. Teammates join through a link. Verified accounts, organizations, and SSO are in early access for teams that want them.

Where does the agent actually run?

On the host's machine, on their own Claude subscription. MobSession streams that session to teammates and relays their prompts back. There is no separate cloud agent running your code somewhere else.

Who can join a session, and how?

Anyone with the link. Each session gets an unguessable link you share with the people you want in the room. They open it and they are in, no signup or install. Every contribution is tagged by name and color, so you always see who steered which turn.

Is my code safe?

The honest picture today: the agent runs on the host's machine, so your code stays where it already lives, and access is gated by an unguessable link rather than a public URL. That link is the access control right now, so anyone who has it can view the session. Share it carefully. Verified identity, roles, a host approval gate, and audit logs are in early access, not generally available yet. See /docs/security-model.

What about my data and prompts?

Session output streams live to whoever is connected. Saved history, retention controls, and audit logs are in early access, so don't assume long-term retention today. We won't claim a certification we don't hold: SOC 2 and formal retention controls are on the early-access roadmap. See /docs/data-and-retention.

Does it cost money?

MobSession runs on your own Claude subscription, so usage bills through Claude as it normally would. There is no separate MobSession charge to start, and each turn shows its duration and cost so the room can watch spend live. Team plans and billing are in early access. Reach out through /contact to talk about a plan.

What model does it use?

Whatever your Claude Code setup uses. MobSession runs on top of Claude Code on the host's machine, so the model is the one tied to the host's own subscription and config.

How do prompts from multiple people work?

They queue and run one turn at a time. While the agent is busy, teammates add prompts, and those run in order. That keeps a shared session coherent instead of letting several people talk over the agent at once.

Can I self-host?

Not yet. Self-hosting is on the early-access roadmap. Today the host runs the agent locally while MobSession handles the live streaming and prompt relay. If self-hosting is a hard requirement, let us know through /contact.

How is this different from screen sharing?

Screen sharing is one-way video. MobSession is interactive: teammates queue prompts that actually run, tagged by name and color, with the web and terminal views in sync and each turn recording its own duration and cost. It is a shared working session, not a broadcast.

What do I need to run it?

Node 22 or newer and Claude Code on the host's machine. Teammates only need the link and a browser. Walk through your first session in /docs/quickstart.

What is generally available versus early access?

Available today: the agent runs on the host's machine with their own Claude subscription, link-based joining with no account, live streaming output, one-turn-at-a-time prompt queueing, name and color attribution, synced terminal and web views, and per-turn duration and cost. In early access: accounts, organizations, SSO, roles, a host approval gate, saved history and ROI views, audit logs, compliance such as SOC 2, retention controls, self-hosting, and billing.