TEAM COLLABORATION
Streams are where the work is talked about
Threaded streams for every piece of work, with people and agents in the same conversation. Whisper threads for the quiet part, shared context for what everyone needs, announcements for what nobody should miss.
Kate Sullivan 09:12Gateway migration is blocked on the refund mapping.
Gaia 09:13That contradicts Tuesday's note in #finance. Want me to reconcile the two?
David Turner 09:15Yes — and file the outcome against the tracker.
whisper · 3 replies, hidden from the streamPeople and agents in the same thread
A stream is the unit of work: everyone who touches it, human or agent, talks in one place. Agents read the whole history, so they answer from what has already been decided rather than asking again.
Threads per project, customer, team or releaseAgents participate as members, not as a sidebarMention a person or an agent by name to pull them inRead receipts show who has actually seen itThe quiet conversation sits beside the loud one
Not every exchange belongs in front of everyone. A whisper thread hangs off a message and stays with it, so the side conversation is findable later instead of lost in a DM.
Whisper threads attached to the message they are aboutShared context: what is decided and what is still openAnnouncements where replies arrive privately, not in the open
Announcements
Action items from this stream4 open · 2 due today · 1 unassigned
Escalates toKate Sullivan, then Grace WhitfieldWhat a stream carries
A private side conversation pinned to the message it is about.
The running answer to "where are we", readable by anyone who joins late.
Broadcast with no public replies, so a notice stays a notice.
Noticed in conversation and filed with an owner and a date.
Who has seen it, so a chase is aimed at the right person.
Every stream knows who it goes to when it stalls.
Kate Sullivan 11:04@Plutus which refunds have been held more than five days?
Plutusthinking · 14sStopWatch an agent think, and stop it mid-thought
Ask an agent something in a stream and it works in the open. Its row says what it is doing right now, how long it has been at it, and what it has already finished. Nobody waits on an answer that is not coming.
Steps appear as they complete, with what each one foundAnyone in the stream can stop a run, not just whoever askedA stopped run keeps its steps as the record of what it didTry again picks up from the ask, not from the beginningEvery kind of stream a company needs
Streams for projects, teams, customers and releases. Public ones anyone can join, private ones you ask to enter, broadcast ones nobody can reply in, and archived ones that stay readable after the work is done.
Public, private, broadcast and archived, all in one browserPrivate streams are listed rather than hidden, so you can askDirect messages with people and with agentsShared context pins records, tables, files and selections into the thread
Browse streams11 in the workspaceThreaded streamsWhisper threadsShared context streamAnnouncementsAction items with ownersRead receiptsMentions for people and agentsFiles and media in threadSearch across streamsEscalation pathsAgent membersStream historyCommon questions
Chats are your customers. Streams are your team — the internal conversation, with agents in it and the work attached.
Yes, within its authority. A digest agent opens one every morning; anything it proposes still waits for a person.
For the people in them. A whisper is private to its participants but it is not lost — it stays attached to the message it came from.
Omnichannel inbox
Video calls & recordings
Bases
Mini apps
Team mail and calendars
Data warehouse
Analytics
Docs, decks & drive
Give the work a thread that remembers
Start with one stream, add an agent to it, and see what it remembers that you would not have.