Multiplayer Sessions

Private Preview

Share a Droid session with teammates in your organization so everyone can follow along, send messages, and steer the same session together.

Private Preview

Multiplayer sessions are in Private Preview and are turned on per organization. Contact your Factory account team to request access. Behavior and labels may change during the preview.

A multiplayer session is a Droid session that several people in your organization work in together. Everyone in the session sees the same transcript live, can send messages, and can steer Droid while it works.

A multiplayer session doesn't run as any one person. It runs as an agent profile, on that profile's computer, with that profile's Git credentials and connectors. That is why setting up an agent profile is the first step.

How it works

  • Shared identity. Droid runs as the agent profile the session was started on. No individual member's personal credentials, connectors, or computer are used.
  • Shared transcript. Members see each message as it streams, who sent it, who is typing, and who is viewing right now.
  • Shared control. Any member can send messages, queue follow-ups, answer permission prompts, and stop Droid.
  • Shared workspace. Members can browse the session's files, review its changes, and open a terminal in the session's folder.

Multiplayer sessions start in two places:

WhereHow a session becomes multiplayer
The Factory AppStart a new shared session, or share a personal session as a shared copy. Teammates join by link or by invitation.
Delegation surfacesDelegate work in a Slack or Microsoft Teams channel, a Google Chat space, or a Linear issue. Teammates who reply join the same session.

Either way, it's the same kind of session: members can open it in the Factory App on desktop or the web.

Before you start

  • Your organization is in the multiplayer sessions Private Preview.
  • Your organization uses Factory-hosted services. Multiplayer sessions aren't available in airgapped deployments. They work even if your organization turns off Session Contents Sync.
  • Your plan includes agent profiles. See agent profiles.
  • Everyone who joins is an active member of the same Factory organization.
  • For delegation surfaces, the delegation app is connected. See Delegations.

Set up an agent profile first

Every multiplayer session runs as an agent profile, which decides the session's computer, repositories, Git credentials, connectors, and default model. Before your team starts sharing sessions, a Manager or Owner sets up the Org Default profile in Settings → Identity → Agent Profiles. Org Default is always offered when someone starts a shared session in the Factory App, and it serves every delegation request that no custom profile serves.

Follow configure an agent profile, and check these for multiplayer sessions:

  • The profile's compute includes the repositories your team works in: its Environment for Dynamic, or its computers for Persistent.
  • The profile can access those repositories and has the Git Credentials and Connectors shared sessions need. Shared sessions clone and push as the agent profile, not as the person who started them. See repository access.
Note

Org Default is built in, but until a Manager or Owner saves it, shared sessions use it as-is: a default model, with no instructions, plugins, or Git credentials. Shared sessions may not be able to reach your repositories until it's set up, so set it up first.

To give a team a different model, Environment, or set of credentials, create a custom agent profile and limit its access to that team. People can start shared sessions only on profiles they have access to. For delegation surfaces, also assign the profile to the app. Anyone in a shared session works with the profile's access, including its connectors, so give each profile only what its work needs.

In the Factory App

In the Factory App on desktop or the web, you can start a new shared session or share one you already started, then invite teammates to it.

Start a shared session

  1. 1
    Open New Session.
  2. 2
    In the computer picker, choose Shared ("Teammates can join by link"). You can also run Create New Shared Session from the command palette.
  3. 3
    Choose an Agent profile. Factory selects the profile you used last, or Org Default.
  4. 4
    Choose a model, or leave it on Profile default, and send your first message.

The session runs on the profile's computer. If that computer is still starting, the session shows Starting the shared computer until it's ready.

Share a personal session

You can turn a session you already started into a multiplayer session. Factory creates a shared copy that runs on an agent profile, titled with "(shared)" after the original title. Your personal session stays as it was, on its own computer.

  1. 1
    In the session header, select Share.
  2. 2
    In Share session, review the options:
    • Agent profile, under More: the profile the copy runs on.
    • Bring unpushed changes: carry your uncommitted and unpushed code changes into the copy. Choose Share without code changes to start from the remote branch instead.
    • Share a summary only: teammates see a short summary of the conversation so far, and Droid gets a detailed one. By default the copy includes the full history.
  3. 3
    Select Next. Factory summarizes the conversation if you asked it to, creates the shared session, and prepares its link.

In the copy, a marker shows where the personal session ended and the shared session began.

The Share option to create a copy is available only to the session's owner, on a session that isn't already shared. To share it:

  • Droid must not be working.
  • The session's computer must be connected and running an up-to-date Droid.
  • The agent profile's computer must have the session's repository.

If something blocks the copy, the dialog says why, for example Wait for Droid to finish working or Reconnect to this session's machine to share it.

Note

Some code changes can't be carried over, such as very large changes or a merge or rebase in progress. Finish or reduce them, or choose Share without code changes.

Invite teammates

Open Share in a shared session to manage who has access.

  • Copy link: anyone in your organization who opens the link sees Join session and becomes a member when they select it. You can also use Copy Sharable Link in the session menu.
  • Add people: search your organization by name or email. People you add get a notice in their Factory inbox.
  • People with access: lists the members. The person who started the session is the Owner.

Every member has the same access: they can view and send messages in the session. There is no view-only member role.

To take someone's access away, select Remove next to their name. To leave a session yourself, select Leave. The last member can't be removed; archive the session instead.

Send messages

Every message shows who sent it. When Droid is busy, new messages wait as steering or queued messages, and every member sees them with the sender's name. You can clear your own pending messages, or all of them.

Mention a teammate with @ to send them an inbox notice. React to a message with an emoji to acknowledge it without interrupting Droid.

Session settings

The agent profile sets the session's connectors, MCP servers, skills, and compute. Members can view them but not change them. Select Shared session settings to see the session's agent profile, model, reasoning, and autonomy.

  • Only the session's owner can change the model.
  • Shared sessions run at High autonomy, and members can't change the autonomy level. See Auto-Run.
  • Any member can answer a permission prompt, but only for that one request. Answers that would allow a command from then on aren't available in shared sessions.
  • Any member can stop Droid.

Work with the session's files

Members can open the session's Changes, Files, and Terminal in the pane beside the chat. Edits and terminal commands run on the agent profile's computer, as the agent profile.

Ambient mode

When several people talk in the same session, not every message is meant for Droid. With ambient mode, Droid decides which untagged messages are meant for it and answers only those. Droid still reads every message as context.

Ambient mode starts once two or more people have typed in a session. It applies only to messages people type in the Factory App.

  • Make sure Droid answers. Include @Droid in your message. Droid always replies to a message that tags it.
  • Get a reply to a held message. When Droid doesn't answer, a Droid stayed quiet row appears under the message. Select Send to ask Droid to reply. The request is posted as a message from you, quoting the held message.
  • Turn it off. Go to Settings → Session Defaults, find Multiplayer, and turn off Ambient mode to have Droid answer every message. Ambient mode is on by default. The setting applies to sessions you start from then on, not to sessions that already exist.

If you don't see the Multiplayer section, ambient mode isn't turned on for your organization yet, and Droid answers every message.

In delegation surfaces

When someone delegates work in a Slack or Microsoft Teams channel, a Google Chat space, or a Linear issue, the session runs as the agent profile that serves them. It's a multiplayer session from the start, with no extra step to share it.

Teammates join by replying

When another member of your Factory organization replies in the thread or issue, their message goes to the same session and they become a member of it. Droid answers each person in turn. If Droid is busy, the message is queued and runs next.

Factory matches people by email. A reply from someone Factory can't match to an active member of your organization is refused, and the session doesn't change. Use the same email in Factory and the delegation app.

Open the session in the Factory App

Members can open the session in the Factory App from the link Droid posts, and keep working there with everything described in In the Factory App.

A shared session that started in a private Slack channel can be joined by link only by members of that channel.

Direct messages stay personal

A direct message to Factory in Slack, Microsoft Teams, or Google Chat runs as the person who sent it, with their own Git credentials and connectors. It's never shared. See personal and shared identity.

Ambient replies in chat threads

In Slack, Microsoft Teams, and Google Chat, your organization can let Droid answer replies in threads it's already working in, even when they don't mention it. A Manager or Owner turns this on or off under Ambient replies in Settings → Delegations. After 24 hours without Droid activity in a thread, mention Droid again to bring it back.

Limitations

  • No CLI support. You can't start, join, or chat in a multiplayer session from the Droid CLI. The CLI's /share command creates an organization view-only link to a session, which is a different feature.
  • No whole-session unshare. Remove members one at a time, or archive the session.
  • Profile settings are fixed per session. Members can't change the session's agent profile, connectors, MCP servers, skills, or autonomy.
  • Ambient mode is still being tuned. The Droid stayed quiet row and how Droid decides when to reply may change during the preview.

Troubleshooting