{"version":"2.1.232","anchor":"shared-global-state-is-being-scoped-per-host","canonical_anchor":"shared-global-state-is-being-scoped-per-host","heading":"Shared global state is being scoped per host","tier":"internal","area":"Session State","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/shared-global-state-is-being-scoped-per-host","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Shared global state is being scoped per host\n\nHost-scoped state jumped from two places to fifty-two, isolating sessions sharing a process.\n\n**What**\n\nState that used to sit in module-level singletons is now looked up per host, covering startup profiling marks, account credit latches, worktree resume refusals and first-party event loggers. Host-scoped lookups go from 2 in the previous build to 52 here.\n\n**Details**\n\n- Ad-hoc warn-once booleans, such as the one for a malformed remote autocompact frame, moved into a shared claim registry.\n\n**Evidence**\n\n`remote_autocompact_frame_drop`\n\n- Area: Session State\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}