{"version":"2.1.295","anchor":"session-registry-liveness-uses-an-identity-check","canonical_anchor":"session-registry-liveness-uses-an-identity-check","heading":"Checking whether a saved session is still running now confirms its identity","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/session-registry-liveness-uses-an-identity-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Checking whether a saved session is still running now confirms its identity\n\nClaude Code's check for which sessions are still live now uses an identity check instead of only testing whether the process exists\n\n**What**\n\nClaude Code keeps a file for each session it thinks is still running. It reads those files to decide which sessions are live. That check has been replaced. It used to test whether the process with the recorded ID still existed and then look at that process. It now uses a check that can also require the process to prove it is the same one.\n\n**Why**\n\nThis may stop an old session being treated as live when its process ID has since been reused by an unrelated program.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}