Chatting with a team

Chatting with a team feels like talking to one person who happens to be backed by several. You message the team, the lead answers first, and as the work moves through different specialties you'll see the speaker change to whoever's actually doing that part. From your side it's still one conversation.

This is the surface you'll spend the most time on once your roster includes a team.

Where team chat lives

Click a team on the Teams page. You land on the team detail page; the Chat tab is the default view. The page has two tabs — Chat and Settings — and most of the time you're on Chat.

The first message

Type into the message box and send. The lead receives the message first — their name and avatar front the response, and they answer or delegate from there. There's no separate "address the team" mode; the lead is the front door.

How handoffs read

As the lead works through your ask, there will be moments where another roster member is the right person for the next part. The lead hands the work over, and that member contributes — you'll see the message bubble's avatar and name change to whoever is doing the work right now. The lead might explicitly bring someone in ("let me bring Imani in for the copy"); Imani's contribution appears next; when the lead picks the conversation back up to wrap things, you'll see them again.

It reads like one conversation moving across a small group. You don't need to manage the handoffs — that's what the lead is for.

Mentioning a specific member

Type @ to mention a member by name. When you @mention someone, the lead steps aside and that member responds to you 1-on-1 for that turn. Useful when you already know who you want — "@imani draft a stronger version of this paragraph" — and don't need the lead to triage.

The lead resumes on your next message unless you @mention someone else.

What you can attach

The same things you can attach to an agent chat:

Files. PDF, CSV, DOCX, TXT, and MD. Drag in or use the attach button. Files are read for the turn you attach them to.
Mentions. @ opens a list of roster members (the bypass behaviour above) and human teammates (for narrative purposes — "draft a reply to @sam").
Implicit context. If you opened the chat from a project, page, or task, that scope is attached automatically.

Suggestion chips

A team can ship with a handful of suggested starter prompts. They appear as chips below the message box on a fresh conversation — click one to send. Catalog teams come with sensible starters; teams you build yourself start blank unless you add prompts in the team's Settings.

Where past conversations live

Every chat with a team is saved in the conversation sidebar on the team page. The sidebar lists both chats and past runs, with filter pills above the list — All / Chats / Runs — to narrow. Conversations are grouped by Today, Yesterday, Previous 7 days, and Previous 30 days, with a search box, and each conversation has its own URL (the ?cid=… parameter on the page) so you can share a link to a specific thread.

What a team chat can produce

Same shape as an agent chat:

A reply in the chat. Text only, nothing saved beyond the conversation.
Pages in the knowledge base. When any member uses page-creating tools, the resulting page opens in a side preview while it's being written and saves to a folder afterwards.
Tasks in a project. When members create or edit tasks, each one appears as a clickable chip that opens the task in the side preview.
Comments on a task. Conclusions and tool-call summaries can post back to the originating task when the chat is scoped to one.

Tips and gotchas

The lead is the front door. Even if your ask sounds like it's "for" a specific specialist, the lead hears it first unless you @mention.
Sent messages can't be edited, and there's no regenerate button on a previous reply. If a turn isn't quite right, send a follow-up — the team keeps the earlier turn in context.
Team chats live alongside team runs in the same sidebar. If you can't find a chat, check that the filter pill is on All or Chats, not stuck on Runs.
The chat surface is per-team. Running a team on a task is a related but separate flow — see Putting an agent on a task, which works the same way for teams.