Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.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

TierUnder the hoodhow much it should matter to you
Useful1my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaFeature Gateswhat it touches
KindInternal Changesin v2.1.277,
Under the hood

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

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