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.261 ·

Bulk per-tool token counting path gated behind two flags, both defaulting off

A bulk per-tool token counting path exists but is gated behind two flags, both off by default.

Nothing to try yet Notable No documentation found In Development
JSON All of v2.1.261
Nothing to try yetTier: how much it should matter to you
4Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
Context ManagementArea: what it touches
In DevelopmentKind: in v2.1.261,
What probably matters to youSection of the release

A new countEach helper can batch-count all tool definitions in a single model call instead of issuing one call per tool, for contextType === "full" contexts. This requires both the tengu_peppy_zephyr and tengu_context_usage_bulk_counts flags to be enabled, and both default to off, so the existing per-tool counting path remains in effect for now.

Read from
Feature flag
tengu_peppy_zephyr 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.261: 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.

tengu_context_usage_bulk_counts 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.261: 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.261. 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_context_usage_bulk_counts, 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_context_usage_bulk_counts, 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_context_usage_bulk_counts, 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_context_usage_bulk_counts, 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
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: tengu_context_usage_bulk_counts

See this entry in the whole of v2.1.261 →

Feedback