Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
WindowsArea: what it touches
Internal ChangesKind: in v2.1.283,
Internal ChangesSection of the release
Unclear It is not known what happens next once one of these errors is reported.
What
On Windows, Claude Code tries to keep a firm hold on your working folder (an anchored backend). If that fails to start, it can fall back to a mode without that hold. It now reports these errors instead of falling back:
EBUSY
EMFILE
ENFILE
ENOMEM
EAGAIN
ETIMEDOUT
EIO
The log line written on fallback now ends "no anchored backend here" instead of "by name".
Why
On Windows, temporary resource problems now show up as errors instead of quietly weakening how Claude Code holds on to your working folder.
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 doubtIt is not known what happens next once one of these errors is reported.
Anthropic's release notes agreeChanged --system-prompt and --append-system-prompt to accept their text and -file forms together; the file's text comes first
