Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.308 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.86 ·

Trusted Device Enrollment

Entry
JSON All of v2.1.86
EntryKind: in v2.1.86,
ChangesSection of the release
What

Claude Code now automatically enrolls your device as a trusted device, sending a X-Trusted-Device-Token header with API requests for enhanced session security.

Details
  • Enrollment happens automatically in the background when you're logged in via OAuth
  • Device is registered with the display name Claude Code on <hostname> · <platform>
  • The token is persisted locally and reused across sessions
  • You can override with the CLAUDE_TRUSTED_DEVICE_TOKEN environment variable
  • Enrollment can be skipped in essential-traffic mode
Evidence

Trusted device enrollment flow (search for "[trusted-device] Enrolled device_id=") — gated by tengu_sessions_elevated_auth_enforcement flag

[Gradual Rollout] — gated by the tengu_sessions_elevated_auth_enforcement feature flag.

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

Read from
Feature flag
tengu_sessions_elevated_auth_enforcement On for this account, and not off by default

The flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.

This account: on · anonymous baseline: on · compiled default in v2.1.86: no gate table built for this version

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

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

What has happened since
Flag reading moved The flag server now returns on for tengu_sessions_elevated_auth_enforcement, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_sessions_elevated_auth_enforcement, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Gate removed from the code v2.1.232 removed the tengu_sessions_elevated_auth_enforcement gate from the code while it was still reading on for the account this site reads. The code path no longer asks a flag before it runs.

See this across every release →

See this entry in the whole of v2.1.86 →

Feedback