{"version":"2.1.290","anchor":"remote-control-403-handling-split-poll-sessions-permission","canonical_anchor":"remote-control-403-handling-split-poll-sessions-permission","heading":"Remote Control separates expired sessions from other access errors","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/remote-control-403-handling-split-poll-sessions-permission","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Remote Control separates expired sessions from other access errors\n\nA 403 on an expired Remote Control session now fails as expired straight away, while other 403s note when a poll-sessions permission is missing\n\n**Unclear.** How the poll-sessions marker is used once it has been passed on is not known.\n\n**What**\n\nA 403 error means the server refused access. For Remote Control, Claude Code now handles these errors in two ways:\n\n- An expired session fails immediately with \"Remote Control session expired.\"\n\n- Any other 403 still gives the \"Access denied (403)\" message. It now also passes on a marker that is set when the error details mention external_poll_sessions.\n\n**Why**\n\nThis lets Claude Code tell a missing permission to poll sessions apart from a general refusal.\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"}