Source Intelligence

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

Remote sessions can be pinned to a single device

Not switched on
Useful3 Signal5
Sessions Notable

A remote session can be pinned to one device, refusing attach from anywhere else.

Device binding on attach is fully wired with detailed outcomes, but its enable predicate is decided outside the source.

What

Attaching to a remote session now checks first whether that session is bound to one device, and registers only when egress is available, an account uuid is present and the local device id matches. Every outcome is reported as tengu_device_bind_attach with a result such as bound, egress, account, no_device_here, other_device, session_unbound or session_unreadable. The whole check sits behind an enable predicate; when it is false or throws, the result is disabled. Nothing in the build sets that predicate's effective value, so it is decided outside the source.

Evidence

tengu_device_bind_attach

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

See this entry in the whole of v2.1.228 →