claude-code - 💡(How to fix) Fix Desktop app shows no recovery option when working directory has been moved or deleted [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#53225Fetched 2026-04-26 05:21:10
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Participants
Timeline (top)
labeled ×3

When a project's working directory is moved or renamed, the Claude desktop app throws an error on startup:

Working directory no longer exists: /path/to/old/folder. The folder may have been moved, deleted, or unmounted.

The app correctly detects the problem but provides no way to recover from within the UI. The only workaround is to manually edit a hidden JSON session file at:

~/Library/Application Support/Claude/claude-code-sessions/<session-id>/<window-id>/local_<id>.json

and update the cwd and originCwd fields to the new path — something most users would never find.

Error Message

When a project's working directory is moved or renamed, the Claude desktop app throws an error on startup: 4. The error appears with no in-app recovery option The error is shown but the user is stuck — no button, no prompt, no in-app fix.

Root Cause

When a project's working directory is moved or renamed, the Claude desktop app throws an error on startup:

Working directory no longer exists: /path/to/old/folder. The folder may have been moved, deleted, or unmounted.

The app correctly detects the problem but provides no way to recover from within the UI. The only workaround is to manually edit a hidden JSON session file at:

~/Library/Application Support/Claude/claude-code-sessions/<session-id>/<window-id>/local_<id>.json

and update the cwd and originCwd fields to the new path — something most users would never find.

Fix Action

Fix / Workaround

The app correctly detects the problem but provides no way to recover from within the UI. The only workaround is to manually edit a hidden JSON session file at:

RAW_BUFFERClick to expand / collapse

Description

When a project's working directory is moved or renamed, the Claude desktop app throws an error on startup:

Working directory no longer exists: /path/to/old/folder. The folder may have been moved, deleted, or unmounted.

The app correctly detects the problem but provides no way to recover from within the UI. The only workaround is to manually edit a hidden JSON session file at:

~/Library/Application Support/Claude/claude-code-sessions/<session-id>/<window-id>/local_<id>.json

and update the cwd and originCwd fields to the new path — something most users would never find.

Steps to Reproduce

  1. Open the Claude desktop app and start a session in a folder (e.g. /Documents/Learning/claude)
  2. Move or rename that folder (e.g. to /Documents/claude)
  3. Reopen the Claude desktop app
  4. The error appears with no in-app recovery option

Expected Behavior

When a saved working directory is missing, the app should offer an in-app option to either:

  • Re-select / re-point to the new folder location
  • Or dismiss / remove the stale session entirely

Actual Behavior

The error is shown but the user is stuck — no button, no prompt, no in-app fix.

Environment

  • macOS 15 (Darwin 24.6.0)
  • Claude desktop app version 2.1.119

extent analysis

TL;DR

The most likely fix is to update the Claude desktop app to handle missing working directories by providing an in-app option to re-select or remove the stale session.

Guidance

  • The error occurs when the working directory is moved or renamed, and the app does not have a mechanism to recover from this situation.
  • To verify the issue, follow the steps to reproduce and check if the error appears with no in-app recovery option.
  • A potential workaround is to manually edit the hidden JSON session file and update the cwd and originCwd fields to the new path, but this is not a user-friendly solution.
  • The app should be updated to handle this scenario by providing an in-app option to either re-select the new folder location or dismiss the stale session entirely.

Example

No code snippet is provided as it is not explicitly stated or strongly implied in the issue.

Notes

The provided information is specific to the Claude desktop app version 2.1.119 on macOS 15, and the solution may vary for different versions or operating systems.

Recommendation

Apply a workaround by manually editing the hidden JSON session file until an updated version of the app is available that handles missing working directories.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Desktop app shows no recovery option when working directory has been moved or deleted [1 participants]