{"version":"2.1.232","anchor":"more-caches-scoped-per-host-instead-of-per-process","canonical_anchor":"more-caches-scoped-per-host-instead-of-per-process","heading":"More caches scoped per host instead of per process","tier":"internal","area":"Session State","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/more-caches-scoped-per-host-instead-of-per-process","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### More caches scoped per host instead of per process\n\nCaches now belong to each Claude Code host rather than the whole process.\n\n**What**\n\nA batch of module-wide singletons now live in a per-host keyed holder, which matters when more than one Claude Code host runs inside a single process.\n\n**Details**\n\n- Moved: terminal capability state, the tmux option probe, startup profiler state including its memory snapshots, MCP and session wiring, bypass-permissions rearm, team store presence, agent file entry cache, bridge subscription, pending model usage, and agent-observed notes.\n- IDE detection also moved and gained `jetbrainsPluginInstalled`, a cache of whether the `claude-code-jetbrains-plugin` is installed, cleared alongside the rest of the IDE state.\n\n**Evidence**\n\n`hasTeamStore`, `jetbrainsPluginInstalled`\n\n- Area: Session State\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}