claude-code - 💡(How to fix) Fix Mac desktop app hard-blocks session when working directory is 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#54615Fetched 2026-04-30 06:40:47
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
Participants
Timeline (top)
labeled ×3

When the working directory of an existing Claude Code session no longer exists (e.g. the folder was deleted, moved, or renamed), the Mac desktop app shows a hard error and blocks the entire session with no recovery path.

Error Message

When the working directory of an existing Claude Code session no longer exists (e.g. the folder was deleted, moved, or renamed), the Mac desktop app shows a hard error and blocks the entire session with no recovery path.

Error message shown

The session is completely blocked with an error. The only workaround is to recreate the deleted folder at the original path so the session can reopen.

Root Cause

When the working directory of an existing Claude Code session no longer exists (e.g. the folder was deleted, moved, or renamed), the Mac desktop app shows a hard error and blocks the entire session with no recovery path.

Fix Action

Fix / Workaround

The session is completely blocked with an error. The only workaround is to recreate the deleted folder at the original path so the session can reopen.

Code Example

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

Summary

When the working directory of an existing Claude Code session no longer exists (e.g. the folder was deleted, moved, or renamed), the Mac desktop app shows a hard error and blocks the entire session with no recovery path.

Error message shown

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

Steps to reproduce

  1. Open a Claude Code session in the Mac desktop app with a working directory set to a local folder.
  2. Delete or move that folder in Finder or Terminal while the session exists.
  3. Attempt to send a message in that session.

Expected behavior

The app should gracefully handle this case — for example:

  • Prompt the user to select a new working directory, or
  • Fall back to the home directory with a warning, or
  • Allow the session to continue in a read-only/no-directory mode

Actual behavior

The session is completely blocked with an error. The only workaround is to recreate the deleted folder at the original path so the session can reopen.

Environment

  • Platform: macOS
  • App: Claude Code desktop app

Additional context

This is a disruptive UX issue — users who reorganize their project folders lose access to session history and context with no in-app recovery option.

extent analysis

TL;DR

The Mac desktop app should be modified to handle the case when the working directory of an existing Claude Code session no longer exists, providing a recovery path such as prompting the user to select a new working directory.

Guidance

  • Investigate the error handling mechanism in the Claude Code desktop app to determine why it blocks the entire session when the working directory is deleted or moved.
  • Consider implementing a fallback strategy, such as prompting the user to select a new working directory or falling back to the home directory with a warning, to provide a recovery path.
  • Review the app's directory monitoring and update logic to ensure it can detect changes to the working directory and respond accordingly.
  • Evaluate the feasibility of allowing the session to continue in a read-only or no-directory mode as a temporary workaround.

Example

No code example is provided due to lack of specific implementation details.

Notes

The solution may require modifications to the app's error handling, directory monitoring, and session management logic. Additionally, the app's UX and UI may need to be updated to accommodate the new recovery path.

Recommendation

Apply a workaround, such as prompting the user to select a new working directory, to provide a recovery path when the working directory is deleted or moved, as this approach can help mitigate the disruptive UX issue without requiring a full app rewrite.

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…

FAQ

Expected behavior

The app should gracefully handle this case — for example:

  • Prompt the user to select a new working directory, or
  • Fall back to the home directory with a warning, or
  • Allow the session to continue in a read-only/no-directory mode

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 Mac desktop app hard-blocks session when working directory is deleted [1 participants]