Follow Discord
Sweep 12 Nov 2026 · 20:38Z Build v2.1.323 540 read Stable v2.1.311 Latest v2.1.322 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial
The last run did not finish v2.1.323 no changelog was produced for this release
HomeReleasesv2.1.283entry #306

Claude Code v2.1.283 ·

More Windows file and I/O errors are recognised by name

Six more Windows NTSTATUS error codes, for memory, open-file limits, device and timeout failures, now map to specific POSIX errors

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

Unclear How Claude Code uses these codes, for example whether it retries on them, is not settled.

What

On Windows, low-level failures are reported as NTSTATUS codes (numeric error codes from the operating system). The table Claude Code uses to turn these into standard POSIX error names, used by file sync among others, gains six entries:

  • NO_MEMORY and INSUFFICIENT_RESOURCES map to ENOMEM
  • TOO_MANY_OPENED_FILES maps to EMFILE
  • IO_DEVICE_ERROR maps to EIO
  • DEVICE_NOT_READY maps to EAGAIN
  • IO_TIMEOUT maps to ETIMEDOUT

Before, these fell through to the default mapping.

Why

When a Windows file operation fails for one of these reasons, the error now names the actual problem, such as running out of memory, too many open files or a timeout, instead of a generic failure.

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 doubtHow Claude Code uses these codes, for example whether it retries on them, is not settled.

See this entry in the whole of v2.1.283 →

Feedback