ENOENT: no such file or directory — page 3

A path Claude Code tried to open does not exist at that location.

1,200 issues · 64 open · 1,136 resolved (95%) · first seen Feb 25, 2025

First response · local

What to do now

Most likely: The operating system rejected a file or directory operation.

  1. Read the first path in the error and verify that it exists and belongs to the expected user.
  2. Check disk space, permissions, symlinks and whether another process holds the target.
  3. Reproduce with the smallest affected path before changing project-wide permissions.

These are conservative triage steps, not an official Anthropic fix. Use the issue and workaround evidence below before making a destructive configuration change.

Is this getting better or worse?

This class of problem is converging. 101 new reports in the last 90 days vs 314 in the 90 before — -68%. The open backlog peaked at 151 in 2026-01 and sits at 64 today.

0 38 76 113 151 2025-022025-082026-022026-08
2025-02 — First reports2026-01 — Peak backlog (151 open)

Derived by counting each matching issue from its creation date until it closed. First-party computation over the anthropics/claude-code tracker — the trend is not published anywhere upstream.

Which builds report this

757 of these reports name the Claude Code build they were running, spanning 137 releases. Heaviest reporters:

Report volume, not a defect count: an issue can mention a build without that build having caused the failure. Versions come from the version string in the bug-report template, matched against real published tags.

Do these get fixed?

Median time to close is 4 days across 1,136 closures. Of the 1,136 closures with a recorded reason, 20% were closed as completed and 911 as not-planned or duplicate. The most recent completed fix landed in 2026-08.

Workarounds reported by the community

210 of these issues post a workaround someone says worked. The highest-engagement ones:

[Bug] VS Code extension: Tool use concurrency error after Jan 23-24 update
✅ WORKAROUND FOUND The fix: Install VS Code extension version 2.1.17 while keeping CLI at 2.1.19 Steps: 1. In VS Code, go to Extensions 2. Find "Claude Code for VS Code" 3. Click the dropdown arrow next to Uninstall → "I…
Found in the thread of #20571 · still open
SSH remote connection fails on Windows — hardcoded /usr/bin/ssh path
I've tried these commands as a workaround but got another error:
Found in the thread of #25659 · resolved
[BUG] VSCode ext - "Fork conversation from here" doesn't do anything
Yes, very appreciate if you can fix it. I mean you have AI on board :)
Found in the thread of #22016 · resolved
Sub-Agents Not Detected: Missing Agents in CLI List Despite Directory Creation
See - there are some workarounds in the comments. This issue (4623) was related to a Windows-specific issue, which has been resolved.
Found in the thread of #4623 · resolved
[Feature Request] Add native Nix/NixOS support or maintain npm installation method
…y @manveru above... It works well for me so far but it is a work-around rather than NixOs support from Anthropic which is still lacking
Found in the thread of #20012 · still open

Excerpts are quoted from the linked issue so you can judge relevance before opening it. Threads that only ask for a workaround, or report that there is none, are excluded. These are community suggestions, not official guidance from Anthropic — read the full thread before applying one.

Matching issues 201–300

Ranked by community engagement (reactions weighted over comments). Listing the top 300 of 1,200 matches; the statistics above cover all 1,200.

Related aggregations

  1. EISDIR: illegal operation on a directory

    495 issues
  2. EACCES / EPERM: permission denied

    415 issues
  3. ENOTEMPTY: directory not empty

    88 issues
  4. EEXIST: file already exists

    138 issues
  5. EBUSY: resource busy or locked

    127 issues
  6. EXDEV: cross-device link not permitted

    91 issues