Share the session, then work together.
Multi-player is not another status update. It is a teammate opening the same agent session, the same spec in progress, or the same hosted agent and moving the work forward.
The next person reconstructs the conversation from Slack fragments.
Alex pasted a wall of context. Nina has to reverse-engineer the spec from the thread. The session itself is not shareable.
I started the webhook replay spec but I want another read before the agent writes code. Here’s a dump of the last 20 turns…
Which version of the spec is current? I’ll start from the last message in this chat.
Without a session link, handoff is a paste.
Send the session, not a wall of context.
Nina opens the live session, reviews the spec in progress, and discusses the next change with Alex and the agent. A Slack link becomes the shared workspace.
I added the missing acceptance case to the spec. Can you continue from that version?
I see the spec update: duplicate delivery after a timeout must replay safely. I’ll update the test matrix first.
With the session, the second person joins the work, not the thread.
Session links, shared hosted agents, and recaps all point at the same durable session stream. Visibility decides who can open it. See Hosted agents and Session recall.
Make your team’s sessions shareable.
Start free and wire the places your team already collaborates around agent work into one session stream.
Fix flaky auth-token refresh test
Tried mocking the clock first — abandoned after the race persisted. Root cause: token cache TTL rounding. Patched in auth/cache.ts, added regression test. Two approaches rejected, one shipped.