Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.283 ·

Idle-session measurement now also tracks time spent waiting on you

The shadow logging that measures idle sessions now records when Claude Code starts and stops waiting for your input, not only when work runs

Nothing to try yet In Development
JSON All of v2.1.283
Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
CompactionArea: what it touches
In DevelopmentKind: in v2.1.283,
In DevelopmentSection of the release

Unclear It is not clear whether the start-of-wait events are also held back by the same flag as the end events.

What

The background measurement that works out how long a session sits idle now tracks a second kind of state. Alongside periods when work is running, it records when Claude Code is waiting for you to respond, and logs a start and an end for each such wait.

The events marking the end of a run are only sent when an internal flag is on. That flag is off unless it is switched on remotely, and it read off both for this site's account and for an anonymous account.

Separately, Claude Code now logs an event whenever it starts or stops advertising a tool host over its bridge connection.

Why

This is observation only and changes nothing you see. It lets Anthropic see how much idle time is spent waiting on the user, which bears on how long the prompt cache (stored context that makes follow-up requests faster and cheaper) is worth keeping alive.

Read from
Feature flag
tengu_dapper_dawn 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.283: 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.283. 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 off for tengu_dapper_dawn, 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 on for tengu_dapper_dawn, 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 off for tengu_dapper_dawn, 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 on for tengu_dapper_dawn, 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 off for tengu_dapper_dawn, 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 on for tengu_dapper_dawn, 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.

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 whether the start-of-wait events are also held back by the same flag as the end events.

See this entry in the whole of v2.1.283 →

Feedback