Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Device BindingArea: what it touches
Internal ChangesKind: in v2.1.280,
Internal ChangesSection of the release
Unclear Whether the tengu_device_bind_skipped gate is on for any account is unread, so it's unclear how this reading applies in practice.
What
When 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.
Why
This 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.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhether the `tengu_device_bind_skipped` gate is on for any account is unread, so it's unclear how this reading applies in practice.
