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

Second condition added to a feature-availability gate for two related capabilities

Two related capabilities now require an extra runtime condition on top of the existing enabled-list check

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

Unclear What the added runtime condition actually checks, and which two capabilities these are, is not established by the evidence.

What

Two nearly identical feature-availability checks, each for a related tool/capability, now require an additional runtime condition (ryn(H0e) and ryn(_Te) respectively) to pass, on top of the existing check against the enabled-features list.

Why

This narrows when these two capabilities are considered available, adding a further runtime condition beyond simply being enabled.

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 doubtWhat the added runtime condition actually checks, and which two capabilities these are, is not established by the evidence.

See this entry in the whole of v2.1.277 →

Feedback