The engine pauses during blocking dialogs and aborts your turn when a command must run now.
What's wrong with this entry?
Binding the engine to a host now pauses it while a blocking dialog is open, mirrors the thinking toggle into the thinking-token budget (zero when off), keeps the engine model in step with the host's main-loop model, and aborts the in-flight turn when a queued command is marked as needing to run now. It also merges salvaged continuation text into displayed message content.
_abortOnNowPriorityCommand
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.224
Loop file can come from stored state instead of disk
Both mention loop
-
v2.1.248
Loop keepalive is on by default
Both mention loop
-
v2.1.248
Self-pacing /loop wakeups no longer blocked by a runtime switch
Both mention loop