{"version":"2.1.280","anchor":"new-device-binding-rejection-reasons-environment-and-targ","canonical_anchor":"new-device-binding-rejection-reasons-environment-and-targ","heading":"New device-binding rejection reason for non-Anthropic-cloud environments","tier":"internal","area":"Device Binding","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-device-binding-rejection-reasons-environment-and-targ","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New device-binding rejection reason for non-Anthropic-cloud environments\n\nDevice\/session binding now refuses byoc and bridge environments with a new 'environment' reason\n\n**Unclear.** The finding does not say what triggers these two new reasons or how they affect user-visible behavior.\n\n**What**\n\nWhen Claude Code binds a session to a device, it checks whether the environment is eligible. There's now a new refusal reason, `environment`, that is returned when the session's environment is `byoc` (bring-your-own-cloud) or `bridge` instead of Anthropic's own cloud. This joins the existing refusal reasons `endpoint`, `pool`, and `correlation`. The check is applied both when device-binder enrollment is prepared (which also now forwards a `confirmReenroll` flag) and when a cloud session is bound to a device, and it feeds into the same reason table used to show the failure message to the user, with a matching telemetry event.\n\n**Why**\n\nThis makes it clear to users and to Claude Code's own logic why a device-binding attempt failed when the session isn't running on Anthropic's own cloud infrastructure, rather than lumping it in with unrelated binding failures.\n\n- Area: Device Binding\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}