Follow Discord
Sweep 28 Sep 2026 · 18:16Z Build v2.1.284 505 read Stable v2.1.277 Latest v2.1.284 Next v2.1.284 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.284 ·

More placeholder file numbers are treated as unusable when identifying files

When identifying a file by its device and inode numbers, Claude Code now ignores more placeholder inode values, including -1 and 2^64

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

Claude Code can tell whether two paths are the same file by pairing a device number with an inode number, a per-file number the filesystem assigns. Some filesystems report a placeholder instead of a real inode number, and Claude Code then does not use it to identify the file.

The set of placeholders it recognises is larger now:

  • 0
  • -1
  • 0xffffffffffffffff
  • 2^64

Before, only 0 and 0xffffffffffffffff were recognised.

Why

On filesystems that report placeholder numbers, such as some network or Windows drives, different files are less likely to be mistaken for the same file.

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 doubtWhether this applies only on Windows, and which features rely on this check, is not known.

See this entry in the whole of v2.1.284 →

Feedback