claude-code - 💡(How to fix) Fix Repo selector [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#56128Fetched 2026-05-05 05:57:29
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
Participants
Timeline (top)
labeled ×2
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

I could have saved so much time if I knew what repo I was working in per claude code chat. IT's still my own fault,but that's how I come up with the ideas lol

Proposed Solution

A project folder, or a pull down bar where you can select which repos you want turned on, and all the chats that are tagged with those repos come up. When claude code agents turn off, you could then still link the same thing that you're working on with the same chat. Like attractor - chats, then readmes, etc.

Alternative Solutions

No response

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

No response

Additional Context

No response

extent analysis

TL;DR

Implementing a project folder or repository selection feature in Claude Code could help users quickly identify and manage chats related to specific repositories.

Guidance

  • Consider adding a feature to display the current repository name in the Claude Code chat interface to provide immediate context.
  • A dropdown menu or filter option for selecting specific repositories could help users focus on relevant chats and reduce confusion.
  • Investigate how to integrate repository information with chat tags to enable easy filtering and organization of chats by repository.
  • Evaluate the feasibility of implementing a "remember repository" feature that persists across Claude Code agent restarts to maintain continuity.

Notes

The proposed solution involves significant changes to the Claude Code interface and functionality, which may require substantial development and testing efforts.

Recommendation

Apply workaround: Implement a manual tracking system, such as using a specific naming convention for chats or creating a separate note to keep track of the current repository, until a more integrated solution is developed.

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

claude-code - 💡(How to fix) Fix Repo selector [1 participants]