When a cloud session cannot bind to your machine, you now get a plain reason why.
What's wrong with this entry?
When a newly created cloud session cannot be tied to the local device, which is what turns off local tools, Claude Code now prints a plain reason instead of leaving it unexplained. Covered cases are device registration failure, hitting the device limit, clock skew, not being logged in, the feature being off server-side, and the server silently dropping the binding.
Not bound to this machine (local tools off):
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.