EEXIST: file already exists

A create or mkdir hit a path that is already taken.

138 issues · 12 open · 126 resolved (91%) · first seen Dec 12, 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. 19 new reports in the last 90 days vs 114 in the 90 before — -83%. The open backlog peaked at 28 in 2026-03 and sits at 12 today.

0 7 14 21 28 2025-122026-032026-062026-08
2025-12 — First reports2026-03 — Peak backlog (28 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

102 of these reports name the Claude Code build they were running, spanning 54 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 126 closures. Of the 126 closures with a recorded reason, 23% were closed as completed and 97 as not-planned or duplicate. The most recent completed fix landed in 2026-07.

Workarounds reported by the community

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

v2.1.69: Freezes on startup on Windows - mkdirSync EEXIST error loop
…th WSL2 - Standalone installer ( ) - Install method: native Workaround Downgrade to v2.1.66:
Found in the description of #30960 · resolved
Write/Edit tools fail with EEXIST on OneDrive directories (v2.1.69 regression)
…ws instead of recognizing the directory as already present. Workaround Writing files via Python through the Bash tool works correctly: The filesystem itself is healthy — only the tool's directory-creation logic is affect…
Found in the description of #30928 · resolved
[BUG] 2.1.69 hangs on Windows after "Yes, I trust this folder" — EEXIST lock path error
…faced to the user — the UI just freezes. Stack trace from : Workaround The npm-installed version at (2.1.64) works correctly. The native installer binary at (2.1.69) is the broken one. Downgrading via npm and ensuring it…
Found in the description of #30932 · resolved
[BUG] Native Windows binary fails on every prompt — EEXIST in OAuth token path
…lect an existing marketplace Update marketplace → EEXIST on Workaround Manual clone + edit : Then add the entry to manually. The marketplace becomes visible in UI, but Update marketplace still fails with EEXIST. Note Thi…
Found in the thread of #27791 · resolved
session-env dir locks and requires manual rmdir to unstick Bash tool on Windows
…ardown the session-env dir; they just reset cwd to default. Workaround users can apply today, if they hit this: rmdir /s /q "C:\Users\User\.claude\session-env\<uuid " (where <uuid is whatever appears in the error). Only…
Found in the description of #49984 · 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 1–100

Ranked by community engagement (reactions weighted over comments).

Related aggregations

  1. ENOENT: no such file or directory

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

    495 issues
  3. EACCES / EPERM: permission denied

    415 issues
  4. ENOTEMPTY: directory not empty

    88 issues
  5. EBUSY: resource busy or locked

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

    91 issues