You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat: Commits tab should default to current worktree branch instead of all branches #620
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.
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.
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.
Activity
Luis-WowApps commentedon Sep 3, 2026
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.
dawNotPoi commentedon Sep 25, 2026
I'd like to take the Commits branch-filter part of this issue. The current default is
null, which callsgit log --all; I plan to default an unsaved selection to the existingHEADfilter, 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.# Release version 0.32.3
# Release version 0.32.3
feat: add ACP v2 support again (spacering-net#620)
test: stabilize e2e approval and cancellation tests (spacering-net#624)
chore(main): release 2.3.0 (spacering-net#619)