{"version":"2.1.323","anchor":"bridge-pointer-standalone-pointers-survive-staleness-withou","canonical_anchor":"bridge-pointer-standalone-pointers-survive-staleness-withou","heading":"Recent standalone Remote Control pointers are no longer deleted when out of date","tier":"internal","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/bridge-pointer-standalone-pointers-survive-staleness-withou","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Recent standalone Remote Control pointers are no longer deleted when out of date\n\nA saved pointer used to reconnect a Remote Control session is now kept when it is out of date, if it is standalone and not too old\n\n**What**\n\nClaude Code keeps a saved pointer that it uses to reconnect a Remote Control session. Before, an out-of-date pointer was always deleted unless deletion was turned off. Now, if the pointer came from a standalone session and is not older than a set limit, Claude Code leaves it in place and simply does not use it.\n\n**Why**\n\nThis can change how resuming a Remote Control session behaves for standalone sessions.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}