claude-code - 💡(How to fix) Fix Desktop: project folder & branch no longer persist between new threads (regression after ~April 8, 2026 update) [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#46393Fetched 2026-04-11 06:21:28
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
labeled ×4

Error Message

Error Messages/Logs

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

After an update on or around April 8, 2026, the selected project folder and git branch no longer persist when starting a new thread in Claude Code Desktop (macOS). Previously, opening a new thread would retain the previously-used project folder and branch. Now, every new thread requires manually re-selecting both the folder and the branch, even when continuing to work on the same project.

What Should Happen?

When opening a new thread, the previously-used project folder and git branch should be pre-selected automatically, as they were before the April 8, 2026 update.

Error Messages/Logs

Steps to Reproduce

  1. Open Claude Code Desktop on macOS
  2. Select a project folder and a git branch in a thread
  3. Work in that thread
  4. Start a new thread (e.g., via the "New Thread" button)
  5. Observe that the project folder and git branch are NOT pre-selected — both must be manually re-selected

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

1.0.123 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

This is a regression noticed after the update around April 8, 2026. The behavior previously worked correctly — new threads would retain the last-used project folder and git branch. This adds friction to every new thread, especially when working on a single project across multiple sessions throughout the day. Note: This bug is specific to Claude Code Desktop (macOS), not the CLI.

extent analysis

TL;DR

  • The most likely fix involves updating the application's configuration or settings to retain the previously-used project folder and git branch when starting a new thread in Claude Code Desktop on macOS.

Guidance

  • Review the application's settings or configuration files for any changes related to project folder and git branch persistence.
  • Check if there are any new options or flags in the Claude Code version 1.0.123 that need to be enabled to retain the previous behavior.
  • Investigate if the issue is related to the Anthropic API or the macOS platform, and if there are any known issues or updates that could resolve the problem.
  • Consider reaching out to the development team or checking the official documentation for any guidance on configuring the application to retain the project folder and git branch.

Example

  • No specific code snippet can be provided without more information about the application's configuration or settings.

Notes

  • The issue seems to be specific to the Claude Code Desktop application on macOS, and the exact cause is unclear without more information about the application's configuration or settings.
  • The fact that this is a regression noticed after an update suggests that the issue may be related to changes in the application's code or configuration.

Recommendation

  • Apply workaround: Until a fix is available, users may need to manually re-select the project folder and git branch for each new thread, or explore alternative configurations or settings that could mitigate the issue.

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