Two hosts in one process no longer share caches, credentials or MCP wiring.
What's wrong with this entry?
State that used to be shared across the whole process is now attached to the individual host, so two hosts in one process no longer share caches, latches and registries. Practically this means one host's launch options, settings source, model string cache, diagnostics, credentials, MCP process wiring and startup-profiling latch cannot bleed into another's.
- A small helper keeps a per-host table of lazily created values and hands them out on request.
- The memory extractor and runner hooks are now looked up against the current session's host rather than a module-level singleton.
hni.of(e.toolUseContext.session.host).extractor?.(e, t)
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