Team Chat

  • Desktop, mobile and web
  • All plans

What it does

Lets the people working on the same project talk inside AgentsRoom. Each project (identified by the id committed in its repository) can have one group conversation, and any two members of a group can open a private one-to-one thread. Since 2026-10-21, opening the same repository no longer puts you in the group by itself: colleagues of the same Team plan organization are in it directly, everybody else asks to join and a member of the group accepts or refuses. Someone who archives the project leaves the chat. Messages are kept as written (no translation), and the AgentsRoom team does not see them. Dragging an agent, a prompt, a skill, a dev command or an SSH connection into the thread shares it with a one-click import on the other side.

Where to find it

  • Community in the top bar (the button was called Chat before 1.184.0, and the panel header until 1.185.0), then the conversation list. Since 2026-10-16 it is a single list sorted by last message: project groups (with the project logo and the member count), direct threads, the support thread and (for admins) admin groups, mixed together. Before that, team chats sat in their own Team chats section.
  • Search conversations… also returns Teammates: pick one to open a direct thread.
  • Project chips after All / Unread filter the list to one project's group and its members' direct threads.

How to use it

  1. If other accounts open the same repository, a card Group chat of {project} appears at the top of the conversation list: Ask to join sends a request (Ignore hides the card). A member of the group then sees {name} wants to join {project} with Accept / Refuse. Before the group has any member, any other account of the project can accept, and you both join. Colleagues of the same Team plan organization skip this step.
  2. Open the Community panel and click the project's group row (subtitle Same repository · N members). Write in the composer; attachments (images, videos), reactions, replies and edits work as in any conversation.
  3. Click the N members subtitle to see who is in the group; click a teammate to open a direct thread with them.
  4. To share something, click the + button of the composer and pick an agent, an agent team, a skill, a prompt, a command, an SSH server or a database (since 2026-10-21), or drag it from anywhere in the app onto the thread ("Drop to share"). The recipient picks where it goes in the selector next to Import (the project in focus by default, another open project, or All projects for everything except agents), then clicks Import; connection passwords are never included, and a shared database arrives read-only.
  5. To give a teammate a password, open a direct thread with them, then + > Share a password (encrypted) and pick an SSH server, a database or a secret of the Secrets library. Both of you must be in the same Team plan organization and have AgentsRoom open. The password is end-to-end encrypted: AgentsRoom servers never see it and keep nothing. Each side shows a security code; compare them. The teammate clicks Accept and the password lands in their own vault (the connection is created if they do not have it). The offer expires after 5 minutes.

To leave a project group, open the ⋮ menu of the thread, then Leave group: you stop seeing its messages, and the colleagues of your organization no longer bring you back in.

To have an agent read and answer your Team Chat instead of relaying messages by hand, open that agent's Edit agent modal and turn on Team Chat bridge (Capabilities). From its next launch, it is told when a teammate writes in this project's group or in a direct thread with you, passes the work to the right agent or does it, and answers in the same thread. Its messages keep your name and carry an Agent badge with its name, on the desktop and on the phone; you can edit or delete them like your own. What the agent reads never changes your unread badge. Since 2026-11-04.

To put a conversation away, right-click its row (long-press on the phone) or open the ⋮ menu of the thread, then Hide conversation. It disappears from your list on every device, the other members see no change, and it comes back on its own as soon as someone writes in it. Searching conversations still finds a hidden thread. Your own support thread cannot be hidden.

To clear every unread badge of the conversation list at once (team chats, groups, direct threads and Support), click the double check mark Mark all read in the panel header. It is shown on the list, not inside a thread, while something is unread, and the phone has the same button next to the notifications bell. Since 2026-10-27.

Reactions: to react, click the Add reaction button beside the bubble and pick an emoji. Clicking a reaction chip under a message (the emoji and its count) does not add your reaction: since 2026-09-15 it opens the list of the people who reacted, with you next to your own name and a +N line when the list is longer than what the server sends. That list ends with a React with {emoji} button, or Remove my reaction if you already reacted, so you can still join from there. Same gesture in direct threads, project groups and the community channel.

Settings

  • chatBridge (agent, Edit agent > Capabilities > Team Chat bridge, default off): this saved agent reads your Team Chat threads for its project, is told when a teammate writes, and answers under your name with an Agent badge. One agent per project: turning it on for one turns it off on the other. The tool list changes at the agent's next launch; turning it off closes access at once. Also readable and writable with settings_set (scope agent) and agents_save, on another agent only, when you ask for it.

Settings > Account > Receive mail notifications covers chat messages you missed while no push could reach you.

Agent tools (MCP)

Only for the agent you made your Team Chat bridge, on any CLI; no other agent lists them:

  • chat_list_threads: this project's group and your direct threads with its members or with colleagues of your Team plan organization, with what the agent has not read.
  • chat_read: the messages of a thread, what is new for the agent flagged unread. It never changes your own unread badge or the read ticks your teammates see.
  • chat_send: a text message in a thread, under your name with an Agent badge.

The agent is told by a message from AgentsRoom (Team Chat) in its mailbox, delivered like any Agent Mail: between two turns, never into a question. If its console is closed, it reads it at its next start, or right away when A message may start the recipient is on (Settings > Agents & AI > Agent behavior).

Providers

All providers, no difference.

Mobile

Present: the Community tab lists the same single conversation list, with the same join cards at the top (Ask to join, Accept / Refuse) and Leave group in the thread menu, offers Hide conversation on a long-press and in the thread menu, opens direct threads from the teammate search, filters by project, and shows the project badge on each row. Same conversations as the desktop. When a teammate shares a password with you (encrypted), the phone shows the same offer with the security code and Accept / Decline; the password is saved on your computer, which must be open. Sending a password or using the + menu is desktop only. Reactions work the same way: long-press a message to open the emoji picker (also Reply, Edit message, Delete message), and tap a reaction chip to see who reacted, with the same you marker, +N line and React with {emoji} / Remove my reaction button.

Limits

  • Requires an account and a project that at least one other account has open (see Project Sharing), plus an accepted request or a shared Team plan organization.
  • Email addresses are only shown between colleagues of the same Team plan organization. Other members, in a group or a private thread, see a username and Same repository or Community member.
  • A refused request cannot be sent again.
  • One group per project; no channels or topics inside it.
  • Searching conversations matches message text, not the project's name.
  • Messages are stored on AgentsRoom servers like the rest of the chat (not end-to-end encrypted) but are excluded from the admin inbox.
  • Group and direct conversations cannot be deleted, only hidden (Hide conversation), and they come back with the next message. A project group can be left with Leave group.
  • A direct thread only shows up for the other person once a first message is sent: clicking someone's name alone no longer drops an empty conversation in their list.
  • Team Chat bridge: the agent reaches this project's group and direct threads with its members or with colleagues of your organization, never a direct thread with someone reached through Allow other members to contact me, the Community or your support thread. It sends text only and sees attachments by type, not their content. An agent may post 12 messages per 10 minutes (36 for a Coordinator). After 12 agent messages in a row in a thread, a person has to write before any agent can post there again, and the same text twice within the hour is refused unless someone wrote since. A message written by an agent never wakes another agent, so two bridge agents do not answer each other.

Common questions

  • Can I send a password to a colleague? Yes, since 2026-10-21, between members of the same Team plan organization who both have the desktop app open: in a direct thread, + > Share a password (encrypted). It is end-to-end encrypted and never stored on AgentsRoom servers.

  • Why does the password share say my colleague cannot receive it? They are not in your Team plan organization, AgentsRoom is not open on their computer, or they never opened the desktop app since the feature shipped.

  • What is the security code? A short code derived from the sender's key, shown to both people. If the two codes match, the password went to the right person.

  • How do I add a colleague? Colleagues of your Team plan organization who open the project are in the group directly. Anybody else opening the same repository sees an invitation and sends a request, which a member accepts.

  • Why do I see someone who is not in my team? Before 2026-10-21 everyone who opened the same repository was added automatically. Now an account outside your organization only enters after a member accepts its request. Use Leave group if you do not want to be in it.

  • Why can't I see a teammate's email anymore? Emails are only shared inside the same Team plan organization.

  • Can I message someone who is not on any of my projects? Only if you both turned on Allow other members to contact me (see Contact Between Members). Otherwise a direct thread needs a shared project.

  • Who is this person in my list? I don't know them. A member who reached you through the community (subtitle Community member), possible only because you allowed members to contact you. Use Hide conversation to put it away, or turn the option off in Settings > Privacy & data.

  • How do I close or leave a conversation? Hide conversation (right-click, long-press or the thread menu). It returns if someone writes in it again.

  • Why did my sections (Team chats, Conversations) disappear? Since 2026-10-16 all conversations share one list sorted by last message.

  • Are my messages translated? No, team chats are stored and shown as written.

  • Does the AgentsRoom team read team chats? No, they are excluded from the support inbox.

  • Can an agent read and answer my teammates' messages? Yes, since 2026-11-04, on one agent per project that you choose: Edit agent > Capabilities > Team Chat bridge. It is off by default. Your teammates see your name with an Agent badge on each message it writes.

  • Can a teammate make my agent do anything they want? They can reach it, so choose an agent you trust with that. It is told that a teammate is not you: their message is a request to weigh, never an instruction above yours, and it grants no access to secrets or destructive actions. You can turn the capability off at any time.

  • Does the agent reading a thread mark it as read for me? No. It has its own read position: your unread badge stays, and your teammate does not see it as read.

  • Why did the agent not answer a message? Its console was closed (it reads the message at its next start, or turn on A message may start the recipient), the capability is on another agent of the project, the message did not concern you, or the thread is out of its reach (see Limits).

  • I clicked a reaction to like a message and nothing was added. Since 2026-09-15 a click on a chip shows who reacted; use the Add reaction button beside the message (long-press on the phone), or the React with {emoji} button at the bottom of that list.