product
Live Thread Sharing
What your team sees when an agent is mid-task.
The Thread is the artifact
When you instruct your agent, three things happen at once:
- Messages stream back to your device. This is the part you already see today.
- The same stream is broadcast to other docked clients in real time. Your iPad shows the same stream as your laptop. So does the project dashboard.
- The Thread — intent, response, file edits, tool calls — is recorded as a structured artifact and summarized into a Recap when it ends.
The third item is what turns a Thread from a private interaction into a coworking event.
Who can see what
Visibility is project-scoped, not host-scoped:
| Role | Sees other Nodes’ Threads? |
|---|---|
| Owner | Yes, all |
| Admin | Yes, all |
| Contributor | Their own Threads + Threads they were granted access to |
| Viewer | Threads explicitly shared with them |
Why “broadcast” and not “polling”
A polled Thread feels like checking up on someone. A broadcast Thread feels like sitting next to them. The technical mechanism is the same WebSocket connection used for everything else.
What this isn’t
This is not a screen share. There is no video. The bandwidth required is text-only — a few KB/s — which is why it works on a phone over LTE.
What this becomes when a Thread ends
When the active Thread closes, the Recap path takes over: a one-paragraph summary lands in Memory and replaces the live stream in the Thread viewer. Late-joiners get the same understanding the people watching live had — without having to scroll back through every message.