{"version":"2.1.236","anchor":"process-wide-state-replaced-by-per-session-containers","canonical_anchor":"process-wide-state-replaced-by-per-session-containers","heading":"Process-wide state replaced by per-session containers","tier":"internal","area":"Session State","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/process-wide-state-replaced-by-per-session-containers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Process-wide state replaced by per-session containers\n\nProcess-wide caches moved per session, groundwork for several sessions sharing one process.\n\n**What**\n\nThe largest change in this release, invisible on its own: dozens of caches and counters that lived once per process now live in a container looked up from the current session. This is the groundwork for more than one Claude Code session sharing a single process without sharing state.\n\n**Details**\n\n- Affected: the OAuth token refresh cache, the clipboard tool probe, Linux and tmux terminal state, the telemetry interaction sequence counter, the sandbox and monitor socket registry, the git repository cache, and the analytics event ring buffer.\n- The holder keys instances off the session object weakly, so they disappear with the session rather than living for the process lifetime.\n\n**Evidence**\n\n`RHb = new en(() => new SOd());`\n\n- Area: Session State\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5"}