{"version":"2.1.304","anchor":"bridge-api-calls-get-enroll-and-retry-pass-through-modes","canonical_anchor":"bridge-api-calls-get-enroll-and-retry-pass-through-modes","heading":"Remote Control connection requests are now labelled to retry or pass through","tier":"internal","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/bridge-api-calls-get-enroll-and-retry-pass-through-modes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Remote Control connection requests are now labelled to retry or pass through\n\nRemote Control register and reconnect requests now use an enroll-and-retry mode, while deregister and archive pass straight through\n\n**Unclear.** Whether these modes change what happens when a Remote Control connection fails to sign in is not stated.\n\n**What**\n\nRemote Control lets you drive a Claude Code session from somewhere else. The requests Claude Code sends to set this up now carry a mode:\n\n- registering and reconnecting use `enroll_and_retry`\n\n- deregistering and archiving use `pass_through`\n\n**Why**\n\nThe names point to registering and reconnecting being able to enroll again and retry after a sign-in failure.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}