What is a multiplayer AI coding workspace?

A multiplayer AI coding workspace is a place where several people work with AI coding agents on one codebase and can see each other doing it: the same sessions, the same changes, the same running app, with each person's actions attributed to them. The phrase is used for three different shapes of product, and the shape decides what a team actually shares. In the first, several people steer one live agent session together. In the second, each person runs their own agent thread on a shared project and the results are merged. In the third, one agent lives in a team chat and works asynchronously on requests. Poly (usepoly.co) is the first shape, which we call multiplayer agentic coding. This page covers all three.

Why the phrase exists

Coding agents such as Claude Code and Codex were built for one person in one terminal. When a team adopts them, every person runs private sessions, and the reasoning behind each change stays in the session that made it. The code gets merged; the understanding does not. "Multiplayer" names the products that put more than one human in the loop with the agents, so the work happens somewhere the team can see.

The three shapes

1. Live steering: several people, one session

One agent, one timeline, several humans steering it as it runs. Everyone sees the same prompt, the same reply and the same change as it happens; any member can answer the agent's question, approve or refuse a change, or stop it. Prompts queue and run one at a time so the agent is never doing two things at once. This is the shape that gives a team a shared record of every decision, and the only one where a person who cannot code can participate as an equal, because the surface is a timeline and approval cards rather than a terminal.

Examples as of September 2026: Poly, Coshell, AQ (as a shared terminal), MobSession, and Omnigent's co-drive mode.

2. Parallel threads: each person their own agent, one project

Each teammate opens their own agent thread on a shared repository; tasks run in isolated copies and are merged later, with a review step at the end. This is how the large builder platforms do multiplayer, because it scales to many people and never blocks anyone. What the team shares is the project and the review, not the session: you find out what a teammate's agent did when the task is ready.

Examples: Replit (own Agent thread per person, tasks merged by the agent), Lovable (drafts a teammate creates and the owner accepts), and Zed's Delta (threads that replicate conversation and worktree, in private beta).

3. An agent in the team chat: one agent, asynchronous requests

An agent joins Slack, Discord or a chat-shaped app as a member. Anyone can mention it; it works in a sandbox and comes back with a pull request or an answer. The team shares the request and the result. Nobody watches the agent work, and steering is a reply in the thread.

Examples: Claude Tag, hilos, Nairi, Bloome, Linzumi, and 143's Slack and Linear triggers.

What "multiplayer" is not

• Multi-agent. Claude Code's Agent Teams and most orchestration frameworks run several agents for one human. More agents, not more people.
• Shared context. A committed CLAUDE.md, a runbook library or a shared prompt set makes separate sessions consistent. It does not put a second person in any of them.
• A multiplayer editor. Zed, VS Code Live Share and Replit's editor let humans co-edit files. Useful, and a different axis from sharing an agent.
• A share link. A read-only transcript of a finished session is a record, not a workspace.

Three things to check, whatever the shape

1. Who can approve. Can any member say yes or no to a change before the agent makes it, from their own screen? In many products the answer is only the person who started the session, or nobody until the pull request.
2. Who spent what. Does each turn say who ran it and what it cost? Products that run on each user's private subscription cannot show this.
3. Where people can talk without prompting. In a shared session, anything typed is an instruction. A channel the agent cannot read is how a team argues about the plan without the argument becoming the prompt.

In September 2026, those three together are rare. They are the reason Poly exists, and the secure shared workspace guide explains the security side of the same choices.

Who makes which

• Live steering: Poly (hosted, Claude and ChatGPT, no keys), Coshell (self-hosted, OpenCode), AQ (shared VM terminal), MobSession (mirrors one Claude Code session), Omnigent (open-source meta-harness with co-drive).
• Parallel threads: Replit, Lovable, Bolt (one prompt at a time in a shared project), Zed Delta.
• Agent in the chat: Claude Tag (Anthropic, Slack), hilos, Nairi, Bloome, Linzumi, 143, Superconductor (ticket-based, with shared implementation chats).

Some sit between shapes; Superconductor lets the whole workspace chat inside any agent's implementation, which is closer to live steering than the rest of its ticket workflow. Our comparisons cover the ones teams ask about most.