Stop Means “No More Sends,” Not “Undo”: Understanding Multi-Agent Cancellation
A cancellation boundary in a multi-agent chat can leave a user message saved, an in-flight reply visible, and later agents uncalled. Those are three different outcomes.
I built OpenClaw Launch, which includes a group chat where one agent can pass work to another. While reading the queue runner, I found a useful reminder for anyone building a “Stop” button around asynchronous work: the location of the cancellation check determines what stops. It does not erase effects that happened before the check.
Consider a group turn with one user message, a front-door agent, and a peer. The runner first copies the previous transcript. Every new line follows this sequence:
append to the turn resultappend to the working transcriptnotify the live UI through onLineawait the persistence write
Only after it emits the user's line does the runner plan agent steps and enter its queue loop. At the top of each iteration, it...
Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE