Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.278 ·

Request-latches class reworked from two Maps to scalar per-session fields

Internal per-session request-latch storage was restructured from two maps to individual fields

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

Unclear The finding does not explain what behavioral difference, if any, this restructuring produces.

What

The internal object that tracks per-session request state (exposed as host.requestLatches) changed how it stores some of its data. Two fields that used to be Maps (key-value lookup structures) are now a plain boolean and two new placeholder fields, alongside other existing maps used for different purposes. This structure backs several internal checks, including ones related to server classifier fallback choices and observed gateways.

Why

This is an internal data-structure change with no direct user-facing effect described, but it underlies features like gateway detection and classifier fallback handling mentioned elsewhere in this release.

Read from
Names in the bundlehost.requestLatches
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 doubtThe finding does not explain what behavioral difference, if any, this restructuring produces.

See this entry in the whole of v2.1.278 →

Feedback