Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.282 ·

Claude Code now tells you when it enrolls this computer as a trusted device

When Claude Code enrolls the computer as a trusted device on its own, it now shows a notice instead of writing only a debug log

Group of 2 You'll notice Improvements
JSON All of v2.1.282
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Trusted DevicesArea: what it touches
ImprovementsKind: in v2.1.282,
ImprovementsSection of the release

What

A trusted device is a computer registered to your account as one you trust. Claude Code can enroll the machine on its own, outside of signing in. Before this release that finished with only a debug log line. Now it shows this notice: "This computer was enrolled as a trusted device for your account (you will also get an email). If you did not expect this, review your devices in claude.ai settings."

  • In the interactive terminal interface, the notice appears as a high-priority notice for 30 seconds, and a warning message is also added to the conversation (automaticEnrollmentNoticePending marks it as waiting to be shown).
  • In non-interactive runs, the notice is logged and written to stderr (the error output), but only when stderr is a terminal.
  • Enrollments that happen as part of sign-in do not show it.

Enrollment, and so the notice, still sits behind the switch tengu_sessions_elevated_auth_enforcement, which falls back to off, and requires your organisation to have require_trusted_devices enabled or allowed. The flag server returned that switch as on for this site's account and for an anonymous baseline account; no reading has been taken under this release yet.

Why

You now learn when a device credential has been issued for your account, and get a pointer to where you can check for one you did not expect.

Read from
Feature flag
tengu_sessions_elevated_auth_enforcement Off by default, switched on for this account

The shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.

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

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.282. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
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 →

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear what, apart from signing in, causes Claude Code to enroll a computer on its own.

See this entry in the whole of v2.1.282 →

Feedback