Multiplayer

In Amp you can work with your colleagues in the same thread and its orb or shared runner, and prompt the agent together:

Activate Multiplayer

To activate multiplayer, open your thread and click the button at the top of the main thread bar.

Confirm in the dialog and multiplayer turns on for 7 days.

Multiplayer is available for threads in two environments: orbs and shared runners. On a runner you share, your own threads qualify when you start them in the workspace you shared the runner with, whatever project they are in. Threads on a runner you have not shared cannot be made multiplayer, because that would give your teammates access to a machine you never shared. If the runner owner stops sharing the runner, multiplayer ends on every thread that was created on it.

Activating multiplayer on a private thread shares the thread with your workspace. To end multiplayer early, click at the top of the thread and choose End Now. Once less than five days remain, the same menu offers Extend Multiplayer, which restarts the 7 days. Multiplayer ends automatically when its time runs out. To set an exact duration, run amp threads share multiplayer ttl <thread> --hours 3 (anything from 5 minutes to 7 days). While it is on, the thread can only start threads in an orb or on a shared runner.

As long as multiplayer is active, your workspace teammates can write prompts in your thread and access the thread’s orb or shared runner, including portals, the terminal, and the file browser. All agent and orb costs are billed to the thread owner.

Security: While multiplayer is active, every workspace member can access the thread, its orb or shared runner, secrets, files, and terminal.

MCP Servers in Multiplayer Threads

The agent calls your remote MCP servers with your credentials, including when a teammate prompts it. To keep a server’s tools out of multiplayer threads, turn off

Integrations in Multiplayer Threads

Some integrations act as you, including when a teammate prompts the agent. While a thread is multiplayer, no one, including you, can use these in it unless you allow it; they work again when multiplayer ends:

• Google
• Your personal Linear installation, for commenting on issues.
• Your own App Store Connect key, including signing on a Mac orb. A workspace key still works.

To allow one, turn on Use in Multiplayer Threads on its card in Settings → Integrations. This guards against accidental use, not a determined contributor.

Linear workspaces your Amp workspace installed follow the same rule for every thread in the workspace. Amp cannot comment through them or read or change their agent routing in a multiplayer thread until a workspace admin turns on Use in Multiplayer Threads for that Linear workspace in workspace settings, under Integrations → Linear.

Slack works differently. Amp can always read public Slack channels in a multiplayer thread, because everyone in your Slack workspace can see them. Private channels, direct messages, and sending messages or reactions, even in public channels, need Allow Private Channels, DMs, and Sending in Multiplayer Threads on the Slack card. This is one permission: enabling sending also allows access to private channels and DMs.

You can also ask Amp to change any of these settings in a thread that is not multiplayer. Amp asks you to approve each change in a dialog.

Tagging Workspace Members

You can tag workspace members with @. Tagging someone automatically invites them to the thread and activates multiplayer.

To talk over voice or video instead, join the thread’s Huddle. It works in every thread and does not require multiplayer.

Workspace members in the same thread can also chat with each other:

Huddle

A Huddle is a voice, video, and screen-sharing call attached to a thread. Open the Huddle pane in a thread to start one. Anyone who can view the thread can join, and you can invite workspace members from inside the Huddle. The call stays connected while you navigate between threads.

Workspace admins can turn Huddles off for everyone in the workspace with the Enable Huddle setting under Members in workspace settings.