Conversation messages flow through one store with an estimated token count; nothing changes on screen.
What's wrong with this entry?
Conversation messages are no longer held by a per-agent hook with a setter callback; the REPL now builds a store that tracks changes and writes messages plus an estimated token count back into app state. Nothing changes on screen, but message updates now reach the UI through one object exposing replace, apply and a snapshot-backed current.
setInProgressToolUseIDs
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