Collaborative Claude Code tools, compared

Claude Code has no built-in way for two people to work in one session, so a team that wants to use it together picks a tool around it. As of September 2026 there are three kinds: Anthropic's own surfaces, which share Claude in Slack or share a finished session read-only; workspaces that put several people in one live Claude Code session; and chat products where a shared Claude Code agent answers requests asynchronously. Poly (usepoly.co) is in the second group. Here are the eleven tools teams ask about, what each shares, and who each is for.

Anthropic's own surfaces

Claude Tag puts one Claude in a Slack channel for Claude Team and Enterprise organizations; anyone in the channel can steer a running session by replying in its thread, and code work lands as a draft pull request. It is the only Anthropic surface where several humans share one agent. Slack only, admin-provisioned, billed from an org balance. Poly vs Claude Tag.

Agent Teams lets one Claude Code session lead several teammate sessions that split work and message each other. It is experimental, off by default, and single-player: one human owns every approval. It is the most-cited page on this topic and it does not put a second person anywhere.

Session sharing on claude.ai/code produces a read-only link to a session; recipients see the latest state when they open it, not live updates. A record, not a workspace.

The open request. Real-time multi-user sessions in Claude Code itself is an open issue (#60082) with no maintainer response as of this writing.

Live shared sessions

Poly runs the real Claude Code agent, and Codex, inside a sandbox on its servers, with a browser room around it: one timeline everyone watches, plain-language approval cards any member can act on before a change lands, a receipt per turn naming who ran it and what it cost, one-click undo, a live preview of the app, and a group chat the agent cannot read. Nobody installs Claude Code or holds a key. Free to start; $20 or $50 a month per person who runs the agent. Its limits: desktop browser only, static publishing, hosted.

Coshell is a self-hosted drive built on OpenCode that runs Claude Code and 70 or more models on your own keys, with one shared session, a named prompt queue, plan approval, follow-along and a shared preview. $0 to self-host. Poly vs Coshell.

AQ runs the real Claude Code CLI on a dedicated VM that teammates join as a shared terminal, editor and preview, each under their own Claude login. Free personal sandbox; Team $50 per user on promotion. Poly vs AQ.

MobSession is a CLI that mirrors one person's local Claude Code session to a share link where teammates watch, queue prompts and react; the host approves prompts by rule and each turn shows its time and cost. Claude Code only, runs on the host's laptop. Free; Team $250 a month flat.

Omnigent is an open-source meta-harness from Databricks that wraps Claude Code and others behind one server; a colleague can attach to your session with Read or Edit access and co-drive, with each message labelled by author. Edit access runs their commands on your machine, and its docs say so. Apache-2.0.

Capacitor (Kurrent) records Claude Code sessions as shared team memory and can launch a hosted Claude Code from a dashboard that anyone with view access can type into and answer permissions for. Free for five seats; $15 per user.

Agents in the team chat

hilos makes agents members of a Slack-shaped chat; a coding run ships a pull request with a report card, and a person approves every merge. Local Claude Code via a daemon or hosted agents on credits. Free; Pro $20, Max $50 per seat.

Nairi puts one org-owned Claude Code, Codex or OpenCode agent in Slack, Discord and a web app; mention it and it works in a container and opens a pull request. No approval step. $20 or $80 a month flat.

Bloome is an agent-first messaging app where Claude Code runs on a teammate's desktop app and joins group chats; the agent is offline when that laptop sleeps. Usage billing from a $0 balance.

Which should you use?

• Your company is on Claude Team or Enterprise and lives in Slack: Claude Tag.
• One person with a large parallel task: Agent Teams.
• A small group, including people who do not code, who want to steer one Claude Code together in a browser with approvals and receipts: Poly.
• A technical team that wants to self-host on its own compute: Coshell.
• Engineers who want a shared cloud terminal: AQ.
• Two people pairing on one laptop's session, cheaply: MobSession.
• A team that wants requests and pull requests in chat rather than a live session: hilos or Nairi.

The Claude Code collaboration guide explains the four underlying options in more depth.