{"version":"2.1.288","anchor":"remote-control-placeholder-sweep-is-stricter-about-server-st","canonical_anchor":"remote-control-placeholder-sweep-is-stricter-about-server-st","heading":"Remote Control placeholder clean-up checks the server before archiving","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/remote-control-placeholder-sweep-is-stricter-about-server-st","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Remote Control placeholder clean-up checks the server before archiving\n\nCleanup of unused Remote Control placeholder sessions now keeps connected sessions and checks title, use and server state before archiving\n\n**Unclear.** It is unclear what records that a placeholder session was used.\n\n**What**\n\nRemote Control lets you drive a Claude Code session from another device. It can create placeholder sessions, and a clean-up pass (the sweep) later removes or archives the ones left over. That pass is now stricter:\n\n- Placeholder records now store optional `titleSha` (a fingerprint of the title) and `usedAt` (when it was used) fields.\n\n- A placeholder whose session is connected, or whose state cannot be read, is kept.\n\n- A placeholder is removed when it was used, retitled, or its `updated_at` time changed. Sessions that are active but disconnected are also removed.\n\n- The local record is read again just before archiving.\n\n- The pass reports how many sessions were not archived because of their server state, and a stamping failure shows as \"[bridge:placeholder] use stamp failed\".\n\nBefore, a placeholder was removed when `updated_at` differed from `created_at` and otherwise archived, using timestamps only.\n\n**Why**\n\nThis stops the clean-up from archiving a Remote Control session that is still connected or has already been used.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}