Session state for commands, tools and MCP config now lives in one object with a lifecycle.
What's wrong with this entry?
The per-session state that drives the interactive session, commands, tools, dynamic MCP configuration, allowed agent types and the main-thread agent definition, moved out of scattered React hooks into one object with an explicit connect and dispose lifecycle. This is how the REPL works on this build; there is no flag.
- Exposes a subscribe/snapshot interface, memoized derivations, and a tool-pool cache keyed on the current permission context and MCP state.
- Must be bound to a host screen before use and throws otherwise.
- Plugin toast and status notifications route through it under
plugin-toast-andplugin-status-keys.
ReplSessionScope: used before its screen bound a host
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.233
REPL state read from a generic per-agent map
Both mention repl
-
v2.1.234
Background REPL evaluations report back into the conversation
Both mention repl
-
v2.1.236
Query handling moved out of the REPL component
Both mention repl