{"version":"2.1.265","anchor":"remote-control-bridge-now-waits-for-in-flight-oauth-refresh","canonical_anchor":"remote-control-bridge-now-waits-for-in-flight-oauth-refresh","heading":"Remote-control bridge now waits for in-flight OAuth refresh before exiting\/registering","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/remote-control-bridge-now-waits-for-in-flight-oauth-refresh","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Remote-control bridge now waits for in-flight OAuth refresh before exiting\/registering\n\nRemote Control now waits for an in-progress login token refresh before registering the device\n\n**What**\n\nWhen you run `claude remote-control` to connect a device (so you can continue a local session from your phone or another computer), the setup process now waits for any in-progress OAuth token refresh (the background renewal of your login credentials) to finish before it registers the device or exits, up to a new capped wait time (`OAUTH_REFRESH_EXIT_WAIT_CAP_MS`).\n\n**Why**\n\nThis avoids a race where Remote Control tries to register or exit while your login token is mid-refresh, which could otherwise leave the connection in a bad state.\n\n- Area: Remote Control\n- Names: `claude remote-control`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}