Desktop app locks to original project folder and cannot be changed

Resolved 💬 2 comments Opened Jun 30, 2026 by ashjudson Closed Jul 4, 2026

Description

Once the desktop app opens with an initial folder, it cannot be redirected to a different folder. All standard workarounds have been attempted without success.

Steps to Reproduce

  1. Open Claude Code desktop app — it roots to an initial folder (e.g. C:\LeaseQuery\WorkArea)
  2. Attempt to switch to a different folder using the in-app "start a new session in a new folder" option
  3. Attempt to close and reopen the app
  4. Attempt to open via File Explorer context menu pointing to a different folder
  5. Attempt to run claude <path> from PowerShell

Expected Behavior

User should be able to open a new session rooted in a different folder without the original folder persisting.

Actual Behavior

  • The "start a new session in a new folder" option appears in the UI but does not work
  • Closing and reopening the app still loads the original folder
  • Running claude <path> from PowerShell opens the CLI terminal version, not the desktop app
  • The desktop app consistently locks back to the original folder regardless of approach

Environment

  • OS: Windows 11 Pro
  • App: Claude Code Desktop
  • Shell: PowerShell

Impact

Users who need to work in multiple separate project folders cannot do so without cross-contamination of context between projects.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗