Desktop: project folder & branch no longer persist between new threads (regression after ~April 8, 2026 update)

Resolved 💬 3 comments Opened Apr 10, 2026 by TGRBTRFLY Closed May 23, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] 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.

View original on GitHub ↗

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