Follow Discord
Sweep 23 Oct 2026 · 21:48Z Build v2.1.310 529 read Stable v2.1.308 Latest v2.1.310 Next v2.1.310 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.310 ·

Device and process file path checks tightened

The check that spots device and process paths such as /proc now normalizes paths and matches more forms, and the Read refusal names them as resolved

Group of 2 You'll notice Improvements
JSON All of v2.1.310
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
File ReadingArea: what it touches
ImprovementsKind: in v2.1.310,
ImprovementsSection of the release

What

Some paths, such as /proc/*/fd/0-2 on Linux, name devices or running processes instead of ordinary files, and the Read tool (which reads files for Claude) does not read them. The check for these paths changed:

  • The check now normalizes a path (rewrites it into one standard form) before testing it, and tests one more pattern, so more spellings and special files are recognised.
  • The Read tool's fixed refusal, "Cannot read '...': this path names a device or process file that this tool does not read.", is replaced by a helper that builds the message from the resolved path spellings. Error code 9 is kept.

The Read tool's own description is unchanged from the previous release in the capture taken under this release.

Why

In practice, paths written in unusual ways that point at a device or process file are now caught by the same safety check instead of slipping past it.

See this entry in the whole of v2.1.310 →

Feedback