You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
AuthArea: what it touches
ImprovementsKind: in v2.1.269,
ImprovementsSection of the release
What
Some sessions are bound to a specific device, so they only accept traffic from that device. When a request from a different device is blocked (an HTTP 403 error classified as "bound_unattested"), Claude Code now shows a specific message explaining this, instead of a generic HTTP error: the session accepts messages only from the device it's bound to, and suggests either sending from that device or running /login to enroll the current one as a trusted device.
Why
This turns a confusing generic error into an actionable one, telling you exactly why access was blocked and how to fix it by enrolling your current device with /login.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added sinceA small documentation edit on Claude Code on Claude Platform on AWS touched a line naming /login after this was published.The `/login` and `/logout` commands don't sign you into a claude.ai subscription for Claude Platform on AWS. Authentication runs through your AWS credentials or workspace API key.claude-platform-on-awssee the edit
Confirmed sinceAnthropic's documentation has since written up /login, on Extend Claude with skills.In [non-interactive sessions](/docs/en/headless), the names `help` and `feedback` aren't reserved for their terminal-only built-in commands, so a plugin skill with one of those names keeps its bare command there. Every other terminal-only …skillssee the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up /login, on Extend Claude with skills.
