{"version":"2.1.265","anchor":"session-keepalive-heartbeat-can-now-be-parked-on-user-and","canonical_anchor":"session-keepalive-heartbeat-can-now-be-parked-on-user-and","heading":"Session keepalive heartbeat can now be 'parked on user' and skip sending","tier":"internal","area":"Session Management","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/session-keepalive-heartbeat-can-now-be-parked-on-user-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Session keepalive heartbeat can now be 'parked on user' and skip sending\n\nSession keepalive heartbeat can now be skipped entirely while 'parked on user'\n\n**What**\n\nClaude Code's session keepalive mechanism (which periodically signals that a session is still active) now checks first whether the session is \"parked on user\" \u2014 a state waiting on the user. If so, it logs a debug event noting the reference count and parked state, and skips the normal heartbeat activity entirely.\n\n**Why**\n\nThis avoids sending unnecessary keepalive signals while a session is simply waiting on the user, which should reduce needless background activity in that state.\n\n- Area: Session Management\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}