{"version":"2.1.315","anchor":"remote-control-ccrturnidendswithturn-variant-and-403-refuse","canonical_anchor":"remote-control-ccrturnidendswithturn-variant-and-403-refuse","heading":"Remote sessions can mark a refused request as blocked by a proxy","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/remote-control-ccrturnidendswithturn-variant-and-403-refuse","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Remote sessions can mark a refused request as blocked by a proxy\n\nRemote sessions can now mark a 403 refusal from the session service as refused by a proxy, and label turns in one of two ways\n\n**What**\n\nA 403 error means a server refused a request because it was not permitted. When the remote session service returns one, Claude Code can now tag it as refused by a proxy, which is a machine sitting between Claude Code and the service. This happens when the caller asks for it.\n\nThe code that labels each turn of a remote session now picks between two ways of doing it, depending on a setting.\n\n**Why**\n\nIn practice, remote sessions can now tell a refusal from a proxy apart from other refusals.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}