Repository navigation
feat: group threads and shared resources by worktree - #12268
Closed
jakeleventhal wants to merge 4 commits into
Closed
jakeleventhal wants to merge 4 commits into
jakeleventhal wants to merge 4 commits into
Conversation
Contributor
Author
|
bruh |
|
Would love to see this come back in some form. I often have multiple threads for the same worktree, and having them grouped together would make the sidebar way easier to manage. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What Changed
Demo video and explanation/rationale
Group conversations by environment, project, and checkout across the web/desktop sidebar and mobile Home/navigation lists. Project, machine, branch, PR, and terminal information appears once per group, while each thread retains its title, provider, and status.
Why
Conversations in the same checkout currently repeat workspace information and can lose access to shared resources when switching threads. Grouping by checkout makes ownership and lifecycle actions consistent while preserving separate conversation histories. Environment-scoped identity keeps identical checkout paths on different machines separate.
Validation
Validation recorded during implementation:
UI Changes
Draft pending hosted before/after screenshots and a short video of whole-worktree drag/reorder. No visual evidence is attached yet.
Remaining before review
Checklist
Implemented with GPT-6 in Codex.