Discussions

Discussions are threaded conversations that live with a project, beside its chats and tasks. Use them the way a team uses a discussion board: open a topic, talk it through, and resolve it — with the project's agents one @mention away. They reuse the chat message surface, so a discussion reads and composes like a chat, but it belongs to the project and every project member sees it, not just its author.

Opening a discussion

Click New discussion, give it a Title, pick a Category, and write the opening message. The categories keep the board scannable: General, Q&A, Ideas, Decisions, Announcements, Show and tell, and Polls. Replies work like any message box — the placeholder says it: Reply… use @ to mention a teammate or agent.

Humans first, agents on request

Discussions are human-first. Your post is always saved as a message between people; an agent only responds when you bring one in.

• @mention an agent in a message and that agent replies in the thread — the same routing and generation as chat, visible to everyone in the project.
• With no @mention, nothing is summoned. A discussion can run its whole life without an agent ever speaking.

This makes discussions the right surface for decisions that need a human record with occasional AI input — ask the agent for the data mid-thread, then decide around it.

Lifecycle

A discussion's category says what it is; its status says where it stands:

• Open — active, the default.
• Resolved — the question is answered or the decision is made. Reopen brings it back any time.
• Locked — no further replies; the chat is disabled with a locked notice. Unlock reverses it.

Resolving is bookkeeping, not archival — resolved discussions stay readable and searchable in the tab.

Turning a discussion into work

Create task spawns a task on the project's board from the discussion, linked back to the conversation it came from — a decision made in a discussion becomes trackable work without retyping it. The discussion remembers the conversion: it shows Converted to task with a View task link, and it can only be converted once.

Where this fits

Discussions fill the gap between a personal chat (one person and an agent) and the task board (work already decided): they are where a team decides. The tasks they spawn flow into Task automation like any other board task, and the @mention mechanics match Agents in chat.