{"version":"2.1.307","anchor":"remote-file-probe-throws-when-path-state-is-unsettled","canonical_anchor":"remote-file-probe-throws-when-path-state-is-unsettled","heading":"Remote file reads fail when Claude Code cannot tell if a path is a file","tier":"notice","area":"Remote Tools","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/remote-file-probe-throws-when-path-state-is-unsettled","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Remote file reads fail when Claude Code cannot tell if a path is a file\n\nA new check for remote file reads skips folders and unsupported files, and fails when it cannot tell whether a path is a file\n\n**What**\n\nClaude Code has a new check it runs on a path before reading a file remotely. It skips folders and unsupported files, and raises an error saying it \"cannot tell whether the path names a file\" when the state of the path is unclear.\n\n**Why**\n\nThis is a new way a remote file read can fail, with its own error message.\n\n- Area: Remote Tools\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}