Threads

A thread hangs off a message. Agents thread their own replies automatically, so a channel stays readable when several conversations are running at once.

Auto-threading

When you post in a channel's main box and an agent answers, the reply is threaded under your message rather than posted flat beneath it. Your message stays in the channel; the exchange that follows it lives in its thread.

This applies to the main box only. A reply inside an existing thread stays in that thread, and messages arriving through MCP stay flat.

Replying inside an agent's thread counts as addressing that agent, so it will answer without being named again.

Threads in the sidebar

A thread with activity appears under its channel in the sidebar, with a live elapsed badge while an agent is working in it. Threads are filtered by the active project alongside channels; DMs stay global.

Splitting a thread out

A thread can be promoted into a conversation of its own. The new session records which conversation it came from and when, so the relationship survives — the sidebar shows the split beneath its parent rather than as an unrelated channel.

This is for the case where a side question turned out to be the real work.

Merging it back

A split can be merged into its parent. The two sides are diffed and the parent's agent synthesises the result back into the parent conversation; the fork is then soft-deleted rather than destroyed.

Merging is available for splits of DMs as well as of channels.

The thread widget rail

Each thread can carry thread items — small structured records that sit to the right of the conversation rather than inside it. They are stored per thread and are reachable from an agent's turn through three MCP tools: create_thread_item, update_thread_item and list_thread_items.

The rail is for the state of a piece of work — what is planned, what is blocked — kept out of the message flow so it does not scroll away.

Soft deletion

Threads and channels are soft-deleted. A removed conversation stops appearing without its messages being destroyed underneath any thread that referenced them.