One worker, one queue

A prompt sent from the browser is added to the exact same queue a locally typed message would go through, processed by the same single worker that runs every turn on that machine, local or remote alike.

This has a concrete practical consequence: a local message and a remote-triggered one can never interleave tool execution or race against each other on the filesystem.

Whichever one arrives first runs to completion first, and the other genuinely waits its turn, exactly as if two people were trying to type into the same terminal at once and had to take turns rather than talking over one another.

A remote-triggered message sent while you happen to also be actively typing locally is not rejected or dropped; it simply enters the same queue and processes once whatever is currently running finishes, the same as any other message would.

This single-queue design is what guarantees checkpoints, covered in Checkpoints and rewind, stay unambiguous even with two possible entry points into the same machine: there is never a moment where it is unclear which turn a given checkpoint belongs to.