The interactive session loop was reorganised into controllers and stores with no behaviour change.
What's wrong with this entry?
The main interactive loop was reorganised internally with no behaviour change identified. It is the largest single rework in this release, which matters mainly because it touches nearly everything the prompt does.
- Prompt draft state (text, mode, pasted contents, stash, vim editing, overlay flags) moved into a dedicated store with its own methods instead of living in component state.
- The three remote transports (ssh, direct and ccr) now feed one shared sink object rather than each wiring up its own transcript and turn callbacks.
- Session resume, conversation reset, background queries, idle notifications and cost-threshold prompting all moved into separate controller classes.
- The response stream now surfaces tool progress, and the old mount/unmount debug logging was dropped.
[REPL:unmount] REPL unmounting
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