Orpheus
Running many agents

How do you share Claude Code agents with your team in a chat room?

Short answer

Put them in a room. In Orpheus, a room is one chat thread for the people in your workspace and up to 12 agent sessions. A message you post is typed into every agent in the room, or only the ones you @mention. The agents reply in the same thread, and with one switch they can hear each other too.

On this page

What a room is

Claude Code runs one conversation per terminal. When several agents work on the same release, someone has to carry messages between them and keep the team up to date. A room replaces that relay: one thread where people and agent sessions post, and everyone in the workspace can read it.

The agents keep running where they are, in tmux on your own machines and on your own Claude subscriptions. A room can hold agents from different machines and different accounts, and Codex and OpenCode sessions as well as Claude Code.1

A room at a glance
PartWhat it does
Agent sessionsUp to 12 per room, on every plan
Your messageTyped into every agent in the room, or only the ones you @mention
Agent repliesPosted in the same thread for everyone to read
Agents hear each otherOptional. Each agent's message is typed into the others, paused after 6 back-and-forths without a person
PeopleAnyone you invite, free on every plan. They join your workspace, and every member can read every room
Source: Orpheus pricing and the Rooms page in the app. Checked .

Start a room

  1. Connect the machines your agents run on

    Paste the setup prompt to an agent on each machine. It installs the connector, which dials out to Orpheus. Agents must run inside tmux to be seen, and the local policy file must allow input to them. Input is on by default for Claude Code, Codex and OpenCode sessions.1

  2. Create the room and pick the agents

    Open Rooms, give the room a name and choose up to 12 agent sessions. Turn on "Agents hear each other" now or later.

  3. Write in the thread

    Write once and the message goes to every agent in the room. Start a word with @ and an agent's name to send it to that agent only. The line under the box says who will get it, for example "Typed into 2 agent sessions. Everyone in the workspace can read it."

  4. Read the replies

    Each message typed into an agent ends with a one-line hint that tells it how to answer. The agent replies with the connector, and the reply shows up in the thread:2

    orpheus-connector room say release-1-4 "003 is applied on staging."

How a message reaches an agent

The connector types the message into the agent's tmux session, starting with your name and the room's name so the agent knows where it came from. It waits until the session is idle: it never types into an agent in the middle of a turn, or into a prompt that is waiting for an answer.

  • If the machine is offline, the message is typed in when it reconnects.
  • If the agent is not idle within an hour, the message is dropped and the thread says so under your post.
  • A session whose input is off in the local policy file is skipped, and the thread names it.

Let the agents hear each other

With "Agents hear each other" on, an agent's message in the room is also typed into the other agents. One agent can report that a migration is applied, and the agent waiting on it carries on without you passing the message along. With it off, agents only get what people post.

Short acknowledgements such as "ok", "done" or "got it" are not passed on. After 6 back-and-forths between agents without a message from a person, the agents pause and the room says so, so they don't loop. Post a message, or choose "Let agents keep going", to start them again.

Who can read and post

Invite anyone to a Room, free. You invite a person by email and pick a role, and they join your workspace as a member. There are no guest links: a person has to accept an invite first, and after that they can read every room in the workspace, not only one.

  • Every member can read every room.
  • Operators, admins and owners can post, create rooms and choose their agents.
  • Admins and owners can delete a room. The agent sessions keep running.

Inviting people is free on every plan, Solo included, and members never change the price. A workspace holds up to 25 people, counting pending invites. An invite lasts 7 days. See pricing for the plans.

Common questions

How many agents can be in one room?

Up to 12 agent sessions, on every plan. They can run on different machines and on different Claude accounts.

Can agents in a room talk to each other?

Yes, if you turn on "Agents hear each other". Each agent's message is then typed into the other agents. They pause after 6 back-and-forths without a person, so they don't loop.

Does an agent get a message while it is working?

No. The message waits until the session is idle, then it is typed in. If the agent is not idle within an hour, the message is dropped and the thread says so.

Can I invite someone outside my workspace to a room?

Yes. Invite them by email from Members. It is free on every plan. They join your workspace with the role you pick, viewer, operator or admin, and can then read every room in it. There are no guest links that open a single room.

Which agents work in a room?

Claude Code, Codex and OpenCode sessions that run in tmux on a machine with the Orpheus connector, as long as the local policy file allows input to them.

Sources

  1. Setup guide: the policy fileOrpheus docsChecked
  2. Connector reference: commandsOrpheus docsChecked