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.239 Home All releases olderv2.1.238 v2.1.240newer
Claude Code v2.1.239

Remote sessions can re-enroll a device after a 403 and retry

You'll notice
Useful2 Signal3
Device Trust

Remote session events no longer get dropped when the server rejects an untrusted device; it re-enrolls and retries.

Feature flag
tengu_violin_wood Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.239: on

Read once, for one account on one subscription tier, against v2.1.239. It isn't a statement about your account. What a flag value here can and cannot tell you

What

Event uploads for remote sessions now send a trusted-device token, and when the server refuses with a 403 for an untrusted device the client can re-enroll and try again rather than dropping the events. Telemetry separates this case from an ordinary success.

Details
  • Parsing the refusal body is behind the tengu_violin_wood gate, which falls back to off, so on a stock build the retry path does not engage.
Evidence

remote_send_event_untrusted_device

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.239 →