Git: read-only commit graph (DAG) viewer with worktree-aware HEADs

[NorfeldtKnowit]

Pre-submit Checks

• I have searched Warp feature requests and there are no duplicates
• I have searched Warp docs and my feature is not there

Describe the solution you'd like?

A read-only commit graph (DAG) viewer for the current repo, equivalent to the VSCode mhutchie.git-graph extension or JetBrains' Git Log tab. Opened as a new pane or tab alongside Warp's Code Review surface.

v1 scope:

• Render a lane-based commit DAG, the visual equivalent of git log --graph --oneline --all.
• Show ref labels on each commit: local branches, remote-tracking branches, tags, HEAD.
• For each linked worktree, render an extra badge on that worktree's HEAD commit, labeled with the worktree folder name. Default scope shows refs from all worktrees of the same repo, since cross-worktree visibility is a primary reason users adopt worktrees.
• Scope picker: All worktrees (default) vs. This worktree only.
• Click a commit, get a side panel: subject, full message, author, date, files-changed list (read-only). "Open diff" hands off to Warp's existing diff / code-review surface; the graph does not own diff rendering itself.
• Click a ref label, focus the graph on that branch (view operation only, not a checkout).
• Search by SHA prefix, commit subject, or author.
• Lazy-load older commits (default page size 500).
• Use the repo's common gitdir as the data source, so the graph is identical regardless of which worktree it was opened from.

Is your feature request related to a problem? Please describe.

To read a project's history visually I currently have to leave Warp for VSCode (Git Graph extension), JetBrains, gitk, or tig. Warp's existing git surfaces (universal prompt branch indicator, the Changes panel in #8542, the file-status tree in #9587) all answer "what changed now?", not "how did we get here, across branches and worktrees?".

Worktrees compound the gap. If I am in feature-x/ worktree and a teammate (or a parallel agent, see #7929) is iterating in feature-y/ worktree of the same repo, I have no in-Warp way to see both branch tips in one graph and tell at a glance which commits are unique to which worktree.

Additional context

Relationship to existing issues (please cross-link, not dedupe):

• Integrated interactive git graph like gitkraken #1297 "Integrated interactive git graph like gitkraken" (open since 2022). Superset that bundles a graph viewer plus interactive rebase, merge conflict UI, PR review, etc. That issue has been stuck on triaged for 4 years partly because its scope is enormous. This new issue intentionally narrows to read-only graph viewing only, so it can ship as a single PR. The full GitKraken vision can build on top.
• Support git worktrees #6870 "Support git worktrees" (closed / completed). Established that Warp recognizes worktrees as indexable repos. This builds on that foundation.
• Parallel agentic coding with Git worktree #7929 "Parallel agentic coding with Git worktree". Adjacent. Agent-spawned worktrees benefit greatly from a graph that surfaces which commits each parallel agent has produced.
• Project Explorer: add Git status file tree for current branch (multi-repo + worktrees) #9587 "Project Explorer: add Git status file tree for current branch (multi-repo + worktrees)". Sibling surface answering "what's changed now". This issue answers "how did we get here". Likely shares worktree-enumeration plumbing.
• Feature Request: Enhance 'Changes' panel with full Git staging, unstaging, and commit capabilities (VS Code-like Source Control UI) #8542 "Enhance 'Changes' panel with full Git staging". Sibling commit-creation surface.

Recommended placement: new tab / pane type, accessible from Project Explorer ("Show graph") and via a keyboard shortcut (suggest Cmd+Shift+G, matching the VSCode Git Graph default). Sits next to the Code Review panel.

Worktree enumeration: git worktree list --porcelain. Read-only, well-supported, fast.

Recommendation on the obvious design fork: when multiple worktrees exist, show every worktree's HEAD as a distinct labeled badge by default, rather than a single "primary" HEAD. Users with worktrees almost always want to see all of them; that is why they have worktrees in the first place.

Explicit non-goals for v1 (please do not broaden during spec):

• No git mutations of any kind: no commit, rebase, merge, cherry-pick, push, pull, branch create / delete, stash apply.
• No conflict resolution UI.
• No PR / GitHub / GitLab integration.
• No reflog or stash visualization.
• No interactive rebase, commit reordering, or squash UI.
• No third-party plugin or extension API.
• No jj (Jujutsu) support in v1, but the data layer should be abstracted enough that adding it later is not a rewrite.
• No new theming surface; graph uses Warp's existing theme accents.

Prior art (in order of relevance):

1. VSCode mhutchie.git-graph, ~6M installs. Gold standard read-only graph viewer.
2. JetBrains IDEs' "Git" tool window, "Log" tab. Strong worktree handling.
3. gitk. Canonical layout reference.
4. tig. TUI version, useful for thinking about keyboard navigation.

Operating system (OS)

macOS

How important is this feature to you?

4

[oz-for-oss]

@NorfeldtKnowit

Here's what I found while triaging this issue:

This looks distinct from #1297: it narrows the request to read-only graph viewing and explicitly keeps mutating Git operations out of v1. The scope is detailed enough to route, but the new graph surface likely needs design mocks before implementation.

Maintainer details

I concluded that well-scoped enhancement request for a read-only Git commit DAG viewer with worktree-aware HEAD badges and integration with existing code review/workspace surfaces..

Triage summary

This is an actionable enhancement request for a read-only Git commit graph/DAG viewer that complements the existing Changes/Code Review and Project Explorer Git surfaces. The request is deliberately narrower than a full Git GUI because v1 excludes mutations such as checkout, merge, rebase, cherry-pick, push/pull, branch management, stash, conflict resolution, and PR-provider integration.

Duplicate check

I enumerated 3,119 open issues via the GitHub API, excluding pull requests and #9732. #1297 is related, but it is a broader GitKraken-style umbrella request that includes interactive/mutating Git workflows, while this issue scopes a read-only graph viewer with worktree-aware HEAD badges. #9587, #9064, #7929, and #9170 are adjacent worktree/code-review issues but do not request the same commit-DAG history viewer. Because fewer than two likely duplicates were found, I am not marking this as a duplicate.

Current implementation notes

• app/src/util/git.rs provides shared Git command helpers and current branch/diff/commit-summary utilities, but not a paged all-ref commit graph query or all-worktree HEAD aggregation.
• app/src/code_review/diff_state.rs and app/src/code_review/git_status_update.rs focus on current repository diff metadata, branch lists, unpushed commits, and file status.
• app/src/code_review/code_review_view.rs / app/src/code_review/mod.rs contain the existing diff/review pane surface that the requested Open diff action could hand off to.
• crates/repo_metadata/src/repositories.rs already detects normal repos, gitfiles, and worktree-style external git dirs, but it stores the active working-tree root as the watched repository rather than exposing a commit-graph/common-gitdir abstraction.
• app/src/tab_configs/new_worktree_modal.rs, app/src/tab_configs/branch_picker.rs, and crates/warp_util/src/worktree_names.rs show current worktree/branch UX plumbing that would be related but insufficient for graph rendering.

Suggested routing

Route through Code Review / Workspace ownership. This likely needs design mocks before implementation because it introduces a new graph pane/tab UI, lane rendering, ref/worktree badges, scope picker, search, lazy loading, and a commit details side panel.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Powered by Oz