Skip to content

feat: Commits tab should default to current worktree branch instead of all branches #620

Closed

Description

@Luis-WowApps

Related UX suggestion:
Consider merging the Changes and Commits tabs into one Git tab, similar to Orca.

That combined view could show, in one place:

  • commit message input / Create PR action
  • changed tracked files
  • untracked files
  • files committed on the current branch
  • commits on the current branch

This would make the worktree state easier to understand because users would not need to switch between separate tabs to answer “what is changed, what is untracked, and what is already committed on this branch?”

Orca's layout makes this clearer: the branch summary, working-tree changes, untracked files, committed branch files, and commit list are visible together for the selected worktree.

Image

Activity

  1. Luis-WowApps commented on Sep 3, 2026

    @Luis-WowApps
    Author

    There is a related multi-worktree case that may sit below this issue. A session starts with one CWD, but the agent can execute commands and modify files in another worktree. CodeG continues showing the original CWD’s branch, so the Changes/Commits views may not show the checkout where work actually occurred.

    This issue addresses filtering commits after the current worktree is known. The additional requirement would be discovering and selecting the active/touched worktree context. I’ll open a separate issue and link it here.

  2. dawNotPoi commented on Sep 25, 2026

    @dawNotPoi
    Contributor

    I'd like to take the Commits branch-filter part of this issue. The current default is null, which calls git log --all; I plan to default an unsaved selection to the existing HEAD filter, while preserving an explicit “All Branches” choice across reopen. I'll cover first open, saved All Branches, folder/worktree switches, detached HEAD, and a deleted saved branch with regression tests. I’ll keep active/touched worktree discovery in the separate issue you mentioned.

  3. added a commit that references this issue on Sep 29, 2026
  4. added a commit that references this issue on Oct 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions