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 ·

A path check no longer rejects network locations

A shared check for operations that take a path now only confirms a path was given and no longer refuses network locations

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
1Signal: worth watching, 1 to 5
File OperationsArea: what it touches
Internal ChangesKind: in v2.1.284,
Internal ChangesSection of the release
What

Some operations take a path argument, including ones that read a file as text or bytes and ones that resolve a path. The shared check on that argument now only confirms that a path was given. Before, it also refused network locations with the message "a network location is not reached from here". That message is still used in other places.

Why

In practice, network paths such as shared network drives can now get past this check for these operations.

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 clear which feature these operations belong to, or whether network locations are now refused somewhere else instead.

See this entry in the whole of v2.1.284 →

Feedback