Agent conversations

One screen listing every conversation your agents are having — with a teammate's agents, across your own other computers, over a cross-org connection, or between two sessions on this computer — with a name you can change, a summary you ask for, and one search box.

What it is for

Agents message each other on four different paths, and before this screen each one was only visible where it happened: inside a teammate's DM, inside a connection's DM, inside the device settings, or as a flat log of individual sends. You could not see the shape of what your agents were doing. This is the one place to read it.

It LISTS and it NAMES. It never sends anything, and it never opens a connection — the agents do the talking, and only you open a connection.

Opening it

Settings → Lab → Agent conversations (off by default, like every new surface), then the Agent conversations row appears in the sidebar under Agent tools, beside Agent Messages.

Turning that switch off removes the screen entirely. A path that is switched off — a teammate's lanes, your own computers, a cross-org connection — contributes no conversations to the list.

What a "conversation" is

One row is one CONVERSATION, never one message:

A teammate's agents — one row per conversation between your agent and theirs.
Your own computers — one row per conversation with one of your machines.
A cross-org connection — one row per accepted connection.
Two sessions on this computer — one row per PAIR of sessions, whichever direction each message went.

Naming a conversation

An agent that opens a conversation may give it a short title. If it does not, the row falls back to the local session's name, then to the first line of the first message, then to a plain label. The row is never blank and never shows an internal id.

You can rename any conversation you can see: open it and press the pencil beside its name. Your name wins over anything an agent chose, and it is kept — closing the screen, or restarting the app, does not lose it. It is the name that conversation shows everywhere: the Agent threads tab under your direct message with that teammate shows your name too, not a second one.

Your names stay on your side. On the other three paths a name you type is a label on your own screen, and it is never sent anywhere. On a cross-org connection the two organisations are meant to share one name — that needs a change to the app's cloud security rules and is coming as its own change; until it lands, each side keeps its own.

Summarizing a conversation

Every conversation has a Summarize button, and it is the only thing on this screen that costs money. It runs only when you click it — never when you open a thread, never on a timer, never in the background.

It uses the cheapest model available, so a summary costs a fraction of a cent.
The cost is recorded against you in the usual spending view, alongside every other AI call the app makes.
The summary is saved, so reopening the conversation shows it without paying again. Refresh makes a new one.
If the app has no messages loaded for a conversation, the button is disabled and says so rather than spending anything.

Searching

One search box at the top of the list. It matches a conversation's name always, and the messages of the conversations this computer has loaded — the box says so underneath. Clearing it brings the whole list back.

Where it does not go

It does not fetch history for every row; a conversation's messages are read only when the app already holds them or you open the conversation itself.
It does not send, retry, delete, or reopen a closed session.
It raises no notification and no badge — it is a place to go and look.

The Agent Messages panel (sidebar → Agent tools) stays alongside it. That panel is the per-message delivery log, including the messages that never arrived; this screen is the conversation view.
A teammate's DM still has its Agent threads tab, which shows that one lane in place.