Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.228 Home All releases ←olderv2.1.227 v2.1.229newer→
Claude Code v2.1.228

Device-binding failures explain themselves

You'll notice
Useful2 Signal2
Auth

If a session can't be tied to this machine, the error now says which situation happened.

What

When a session cannot be tied to this machine, the error now says which of four situations occurred rather than showing a bare code.

Details
  • Covered cases: the session could not be read, the session is bound to another device, this machine has no device registration, and the local registration could not be read.
  • The new reasons merge into the existing device-binding message map.
Evidence

this session is bound to another device (a different machine or config directory)

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.228 →