{"version":"2.1.318","anchor":"ccr-worker-requests-outsideitslane-option","canonical_anchor":"ccr-worker-requests-outsideitslane-option","heading":"Remote session workers can mark a request so its permission errors are counted apart","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/ccr-worker-requests-outsideitslane-option","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Remote session workers can mark a request so its permission errors are counted apart\n\nRemote session workers can flag a request so a refused-permission error on it no longer adds to the count of repeated errors\n\n**What**\n\nWhen Claude Code runs as a worker for a remote session, it keeps a running count of short-lived \"403\" errors, which are replies saying a request was refused permission. It uses that count to decide when the errors are serious. A request can now be marked with an `outsideItsLane` option. For a request marked this way:\n\n- A 403 that does not come from the session's own origin is left out of the running count.\n\n- A successful reply no longer resets the count for that request.\n\nBefore, every request fed into the same count.\n\n**Why**\n\nRequests that normally fall outside a worker's usual work can no longer push the count up. This should mean fewer remote sessions treat a passing permission error as a real sign-in problem.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}