Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [FEATURE] Better worktree/branch management in the mac app [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#45211•Fetched 2026-04-09 08:10:41
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
connerdrewconnerdrew
Participants
connerdrewconnerdrew
Timeline (top)
labeled ×3
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • This is a single feature request (not multiple features)

Problem Statement

Creating a new branch/worktree with a specific name is cumbersome and often results in claude being confused as to which branch/worktree the session should be in.

Proposed Solution

There are plenty of bug reports on how claude code on the mac app doesnt display or stiay to the session's worktree/branch, but I'd like to request similarly to how other AI coding apps work, I'd like to be able create a new worktree from the mac UI rather than only selecting existing branches or worktrees.

I also have a hunch this might help the mac app stay in that new branch rather than having to create and switch through messages.

This would also use less tokens and be a faster workflow.

Alternative Solutions

No response

Priority

High - Significant impact on productivity

Feature Category

Other

Use Case Example

Every time I need to create a new branch or worktree

  1. new session
  2. create new branch/worktree
  3. type in the desired branch or worktree name with prefix auto-populated
  4. start coding with the new branch

Additional Context

No response

extent analysis

TL;DR

Implementing a feature to create new branches or worktrees directly from the Mac UI could simplify the workflow and reduce confusion.

Guidance

  • Investigate existing Git workflows and UI designs in other AI coding apps to inform the design of the new feature.
  • Consider the technical requirements for creating new branches or worktrees, such as handling naming conflicts and updating the session state.
  • Evaluate the potential benefits of reducing token usage and improving workflow speed.
  • Review the current implementation of branch and worktree selection in the Mac app to identify areas for improvement.

Example

No specific code example is provided, as the issue focuses on a high-level feature request.

Notes

The proposed solution aims to address a specific pain point in the current workflow, but its implementation may depend on various technical factors, such as the underlying Git architecture and the Mac app's UI framework.

Recommendation

Apply workaround: Implement a feature to create new branches or worktrees directly from the Mac UI, as it could significantly improve productivity and reduce confusion.

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…
#memory optimization#batch processing#GPU compatibility#latency issue#model 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