Under the hood
Useful2 Signal2
Interactive session state was consolidated into one object; an out-of-order safety check was dropped.
What's wrong with this entry?
Anonymous. No account, no email.
What
About a dozen separate pieces of interactive-session state, including pending query parameters, streaming text and tool-use updates, and swarm timing and budget info, become fields on one object, with callbacks passed as named methods. No behaviour change, though an internal consistency check that used to throw on out-of-order sends is gone.
Evidence
deferredSlashEchoUuid
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.234
Background REPL evaluations report back into the conversation
Both mention repl
-
v2.1.248
Prompt submission and composer state moved into dedicated controllers
Both mention repl
-
v2.1.248
Prompt input takes grouped objects and drops some handler guards
Both mention repl