Follow Discord
Sweep 29 Sep 2026 · 18:10Z Build v2.1.285 506 read Stable v2.1.280 Latest v2.1.285 Next v2.1.285 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.285 ·

Startup wait for feature settings reorganised and now recorded

How Claude Code decides whether to wait for feature settings at startup was reorganised, and the wait is now recorded

Under the hood Internal Changes
JSON All of v2.1.285
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
InternalsArea: what it touches
Internal ChangesKind: in v2.1.285,
Internal ChangesSection of the release
What

At startup Claude Code may wait for feature flags, remote switches that turn parts of it on or off. The decision to wait changed: it now comes from shared checks that consider the time available, whether settings are still pending, whether a saved copy is empty, and whether an early fetch was started. The old decision and the recheck for switched-off features remain, and the wait is now recorded in Claude Code's usage data.

Why

The main visible difference is in what gets recorded about the startup wait.

Read from
Feature flag
tengu_auto_mode_config Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.285: not a boolean we can read

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

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 unclear whether how long startup waits has itself changed.

See this entry in the whole of v2.1.285 →

Feedback