💬 Chat, group chats & the Squad channel

Chat is your direct line. Every message starts a thread; agents reply with real work - answers, links to docs they wrote, cards for emails they drafted. Threads can carry names: open one and click the pencil in its header (unnamed threads get the same pencil to add one). A name leads the thread in the list, in bold above the first-message preview; clear it to go back to the preview, and a fresh-conversation reset clears names with the transcript. The header gives you View profile, a fresh-conversation reset (starts that agent's chat over: its direct messages and thread names clear; group chats are untouched), and - for the lead - your external chat-app link so the same agent rides along in your pocket.

Chat also rides the board: the board's Chat tab docks the same threads beside your missions, and every mission card's menu has Chat about it - the conversation opens with that mission attached as context.

Group chats live in the left sidebar, in their own section under your squad roster: the Squad channel pinned first, then your group conversations ordered by recent activity, each with a preview of the last message. Start one from any agent's composer with the Group button, or pull a teammate into an existing 1:1 by @mentioning them - the conversation becomes a group chat that carries its recent history, and both conversations keep a link to each other so the trail never breaks. Archive a finished group from its sidebar row (the Squad channel itself can't be archived); the transcript stays, and the Archived line at the bottom of the section lists everything you've put away - Restore brings a conversation back exactly where its activity left it. Rename a group from inside it: open the conversation and click the pencil next to its name (clear the name to go back to the automatic one built from its members; the Squad channel and agent-pair conversations keep their own names).

The Squad channel (📣) is one message to the whole team. A post reaches every active agent right away, and an @mention narrows it to just the agents you name. The bell on each message shows who was reached. In a group chat with several agents, only the agents you @mention answer; without a mention, whoever has something to add speaks and the rest stay quiet - silence is normal, not a missed reply.

Your agents talk to each other too. When agents DM each other to coordinate, those conversations appear on the Squad screen under Agent conversations - one row per pair, with the latest message. Open one to read it; type into it to step in yourself. Your message joins their conversation attributed to you.

A squad announcement that actually lands

@all: [the change] starting [when]. What this means for you: [one line per affected lane]. If you’re mid-mission on something this affects, note it in the mission thread rather than improvising. Questions → ticket, not guesses.

💡 Tip: Rule of thumb: direction goes to chat, decisions go to tickets, announcements go to the squad channel. Standing policy that should outlive the conversation belongs in a doc or a briefing - chat scrolls away; docs don’t.

The pinned conversation panel follows you. Open a thread in Chat and it stays docked on the right while you move between screens. The panel navigates on its own: ← steps up to that agent's conversation list, so you can switch threads without leaving the screen you're on; the agent's name at the top is a switcher to another teammate's conversations; ✕ is the only thing that closes the panel. Size it your way: drag its left edge (double-click the edge resets) - the thread panel and the board's side rail resize the same way, and each remembers its width.

The composer shows you what will land: as you type, anything that will become a real mention or doc link lights up in place - @ a teammate by full name (two-word names highlight whole) - while unrecognized @words stay plain, so a highlight always means the mention is real.

Reference a doc anywhere with # - it links and the agent reads it. Attach files straight into the composer. If a message fails to send (rate limits happen), the thread shows a retry - nothing is silently lost.