EACCES / EPERM: permission denied — page 2

The OS refused a read, write, or exec because of file ownership or mode.

415 issues · 71 open · 344 resolved (83%) · first seen Feb 24, 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 holding steady. 99 new reports in the last 90 days vs 130 in the 90 before — -24%. The open backlog peaked at 71 in 2026-08 and sits at 71 today.

0 18 36 53 71 2025-022025-082026-022026-08
2025-02 — First reports2026-04 — Most new reports (64)2026-08 — Peak backlog (71 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

262 of these reports name the Claude Code build they were running, spanning 122 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 28 days across 344 closures. Of the 344 closures with a recorded reason, 15% were closed as completed and 293 as not-planned or duplicate. The most recent completed fix landed in 2026-08.

Workarounds reported by the community

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

Sandbox: allow outbound connections to localhost
…e of these settings allow the outbound connection. The only workaround is either on every bash call, or adding the command to , both of which defeat the purpose of the sandbox. Requested feature A sandbox setting that al…
Found in the description of #28018 · still open
[BUG] Background tasks ignore $TMPDIR and hardcode /tmp/claude/
To work around this problem, I did this: This is the version with the bug. First thing, disable auto update by adding this to : If you are still on version 2.0.76 you're good. If you are on 2.1.1 then you also have to do…
Found in the thread of #15700 · resolved
[BUG] claude-code for Windows is NOT available due to its port
I had this error too. you can avoid it by patching the file and replacing the with a lower port, e.g. <img width="542" height="201" alt="Image" src=" /
Found in the thread of #3402 · resolved
Sandboxed Bash intermittently fails: apply-seccomp: unshare(CLONE_NEWUSER): Invalid argument
…thread , if the helper's entry point can run early enough. Workarounds, for anyone else hitting this What we shipped: a small wrapper early on that rewrites the prefix to run under first. util-linux is single-threaded,…
Found in the description of #86928 · still open
[Feature Request] Multi-account/profile support with CLI flags
…in to switch accounts - Use the web version for one account as a workaround Requested feature: Native support for multiple accounts/profiles, similar to how Chrome handles different Google accounts. Ideally: 1. Ability t…
Found in the description of #19722 · resolved

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 101–200

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

Related aggregations

  1. ENOENT: no such file or directory

    1,200 issues
  2. EISDIR: illegal operation on a directory

    495 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