Under the hood
Useful2 Signal3
The pending command queue is per session now instead of shared across the process.
What's wrong with this entry?
Anonymous. No account, no email.
What
Prompt input, queue-edit hotkeys, background loops and agent spawning read the queue of pending commands from an object handed to them rather than from module-level variables, making it per session instead of process-wide. The queue also travels through tool context, and task notifications are enqueued through it.
Evidence
t.messageQueue.enqueuePendingNotification({
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.235
Process-wide caches are now scoped per host
Both mention state
-
v2.1.235
Per-session state replaces process-wide globals, and the render root takes explicit dependencies
Both mention state
-
v2.1.235
More file-scope variables replaced by accessor-backed containers
Both mention state