Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
CompactionArea: what it touches
Internal ChangesKind: in v2.1.260,
Internal ChangesSection of the release
Compaction now uses a new helper to decide, per-compaction, whether trailing thinking blocks in the kept tail should be stripped, based on the resolved model and thinking type. It logs the decision, whether from an env override, the thinking_type default, or a flag, and marks the boundary with a thinking_stripped marker when stripping occurs.
During reactive compaction, preserved messages now pass through a new step that may strip thinking blocks and insert a marker attachment, with new telemetry fields tracking how many thinking blocks were kept versus stripped and what determined the decision.
Read from
Names in the bundlethinking_stripped
Feature flag
tengu_wise_cometOff 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.260: 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.
Flag reading movedThe flag server now returns off for tengu_wise_comet, 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.