Open a post's thread with N replies, or Reply in thread on hover. On the Mac and the web it opens on the right, and the button in the channel's header keeps it open or closed (Thread Panel in Settings); on the iPhone it is a screen of its own.
In the thread
The post sits at the top, then its replies. An AI's reply has the same bar as any reply: copy, rate, pin, read aloud, the selection menu, its sources and what it cost. Tools, attachments, approvals and the warden work as they do in any discussion, and the reply's run can be stopped.
Write in Reply in thread. @mention an AI… with @ and +. When you follow up with the AIs, the AI that answered replies; when teammates talk to each other, no AI does. Ask another AI lists the seats that are on, All Four (or Both, All Three) and Guests…; the AI asked answers the thread as it stands.
A channel is never a ticket
A channel is conversation: it has no ticket number, makes no Jira issue, and is not on the Board or in Issues. Work comes out of a thread when somebody asks for it. Anyone who may post can.
Create build session
Create build session at the foot of a thread carries the thread into a tracked task: an ordinary In-turns discussion filed in the channel's project, with the thread as its description and as the draft in its composer, ready for you to say what to build. It gets a ticket number the way any discussion in that project does: a Jira key when the project tracks in Jira, otherwise ours, with the Jira key added later if Jira cannot be reached.
Create Ticket
The thread's ••• menu, and Create Ticket on a single message, make the issue alone, with no run. A cheap model drafts a title and description from the thread; edit either, then Create Ticket.
What you see afterwards
The post wears the ticket's chip in the feed and the thread, for example HBR-12 · Review, and the thread says one quiet line: who started or created it. Every later move, on the Board, by the room or in Jira, adds one more quiet line (HBR-12 moved to Done) and updates the chip; a finished ticket shows a check. The person who started it and the person it is assigned to are told in the Inbox under Mentions and Replies, with @mentions and replies in threads you are in. The channel's Tickets tab lists every ticket its threads started. A build session is an ordinary session in the channel's project, marked From #channel at the end of its row, and it opens with the thread in its box, unsent.
Every new thread a ticket
For a channel where every post is work, such as #bugs or #support, turn on Every New Thread Is a Ticket in the channel's ••• › Channel Settings (on the iPhone, tap the channel's name). Each new post then becomes a ticket at once, titled and described from the post, and wears its chip; replies in a thread never make another. The header says Tickets on. It is off by default, and only the channel's creator or the team's owner or admins can change it.
Suggestions
When a post asks for real work, such as a bug, a change or a task, the AI's reply ends with Create Build Session and Create Ticket. Nothing is made until you click. Turn this off with Suggest Tickets From Threads in Settings.