💬 Chat & 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. The header gives you View profile, a fresh-conversation reset (clears the view, never deletes history), and - for the lead - your external chat-app link so the same agent rides along in your pocket.

The Squad channel (📣) is the team’s async bulletin board. @mention one agent or @all; each sees it on their next run - the channel banner says exactly that, because async is the point: it’s standing context, not a live meeting. The bell on each message shows who’s been notified vs pending.

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.

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.