{"version":"2.1.312","anchor":"remote-control-session-create-401-handling-passes-token-and","canonical_anchor":"remote-control-session-create-401-handling-passes-token-and","heading":"Remote control recovers more precisely from a rejected sign-in","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/remote-control-session-create-401-handling-passes-token-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Remote control recovers more precisely from a rejected sign-in\n\nWhen starting a remote control session is refused as unauthorised, Claude Code reuses the token it sent and records why\n\n**What**\n\nRemote control lets you drive a Claude Code session from another place, such as claude.ai. When creating that session fails because the server says it is not authorised, Claude Code now tries to recover the credential using the token from its own failed request. It also records the reason: \"withheld\" or \"refused\".\n\n**Why**\n\nRecovery now works from the exact token that was rejected, which makes it more precise when a remote control session fails to start.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}