{"version":"2.1.311","anchor":"remote-control-session-creation-uses-a-host-sessions-bearer","canonical_anchor":"remote-control-session-creation-uses-a-host-sessions-bearer","heading":"Remote Control sessions can sign in with a host-provided token and recover from rejections","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/remote-control-session-creation-uses-a-host-sessions-bearer","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Remote Control sessions can sign in with a host-provided token and recover from rejections\n\nCreating and looking up Remote Control sessions now tries a host-provided token first and refreshes it in the background when it is rejected\n\n**What**\n\nRemote Control lets you work with a Claude Code session from another device. When Claude Code creates or looks up a Remote Control session, it now first tries a sign-in token supplied by the host it runs on. If there is none, it falls back to your normal account sign-in. Before, it always used your normal account sign-in.\n\nIf the server rejects the request as unauthorised, Claude Code now tries to recover the host token in the background.\n\n**Why**\n\nThis changes how hosted Remote Control sessions prove who they are, and helps them recover when a token stops working.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}