Conversations
Threaded chats with operators — when to use them, how they differ from work items, and what operators do during a thread.
Conversations are the everyday way to talk to operators. Open a thread, send a message, watch them work. Threads persist — they're how operators retain context across sessions.
The left sidebar has a Menu ↔ Conversations toggle at the top — flip to Conversations view to see your active threads grouped by recency (Today, Yesterday, This week, …), with quick-actions for archive, delete, and rename.
When to use a conversation vs a work item
| If you want… | Open a… |
|---|---|
| Quick question, ad-hoc help, brainstorming | Conversation |
| Tracked deliverable with status, owner, deadline | Work item |
| Recurring scheduled job (daily report, weekly digest) | Routine |
Conversations are great for the 80% of work that's "just answer this" or "draft that". Work items are for the 20% that needs visibility, sign-off, or tracking.
What happens during a conversation
When you send a message:
- The operator reads the message + relevant memory + workspace files in scope.
- They decide: respond, act with a tool, or escalate.
- Acts that need approval (sending an email, paying a bill, deploying code) surface as approval cards. Click approve or reject.
- Streamed responses appear inline as text + cards (artifacts, file edits, tool calls).
Long-running threads can be subscribed to — the operator notifies you when something changes (a build finished, a customer replied, a deadline approached).
Anatomy of a thread
Conversation
├─ Participants you + one or more operators
├─ Messages your text + operator replies + tool calls + artifacts
├─ Subscriptions notifications you've opted into
└─ Memory writeback after each turn, the operator updates its memoryMulti-operator conversations
Add more operators to the same thread to get a small group. Every operator sees the full thread; they decide whether to respond based on their role and what's been said. To prevent every operator from chiming in on every message, operators can pass — they observe but don't reply unless their input is warranted.
This makes it possible to run a brief team standup in chat: a PM operator proposes a plan, a designer operator critiques it, an engineer operator estimates effort.
What's next
- Work items — for tracked deliverables
- Operators — what's actually responding to you