[Feature]: Add a Git history view

[isaachorowitz]

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the request.

Area

apps/web

Problem or use case

I want to inspect the Git history of the current project from inside T3 Code. At the moment there is no obvious way to browse previous commits and understand how the project reached its current state.

Expected behavior

Provide a Git history surface that shows, at minimum:

• Commit list with message, author, and date.
• Branch/ref context.
• The files changed by a selected commit.
• A diff for the selected commit.
• Useful navigation from a changed file or diff back to its commit.

The initial version could focus on local repository history and avoid remote-provider features.

Smallest useful scope

Add a “History” view for the active repository backed by local Git log data, with commit selection and commit diff inspection.

Why this matters

Git history is essential for reviewing agent work, diagnosing regressions, understanding prior decisions, and comparing the current state with earlier commits.

Related

Related but distinct: #5881 requests per-commit views in the Diff pane; this request is for a general, discoverable Git history browser.

Contribution

• I would be open to helping implement this.

[Quicksaver]

#15187 proposes a Version Control panel that includes branch history and comparison with a base, backed by local Git and with provider data only as an extra.

[bolexyro]

I had the same problem. I kept opening VS Code solely to use the Git Graph extension, and hated having to switch apps just to inspect history. So I built a Git Graph-style history view inside T3 Code.

t3.git.graph.mp4

The current implementation adds approximately 6.3k lines. Before opening a PR, would this direction fit T3 Code, and what scope would you be comfortable reviewing?

[bolexyro]

@t3dotgg I think this might be worth considering. PLEASEEE take a look at this

[bfozturk]

Looking for the same +1

[paveltar]

Would be awesome!

[Ragulsundaram]

+1 from a daily T3 Code user. The thing I miss most from Cursor is the GRAPH section under Source Control: the commit list with branch lanes, so I can see where main is and what my agents just committed without leaving T3 Code.

Maintainers, is this a direction you'd accept a PR for? If yes, I'm happy to build it. Scope I'd propose: a read-only graph (commits, branch/tag labels, lanes), click a commit to see its changed files in the existing diff panel. No checkout/rebase actions in v1.

[djgilcrease]

NOTE: This comment was left by gpt-6.1-sol high on behalf of Dj Gilcrease.

A small read-only Git History Explorer is now released as an independent plugin: digitalxero/t3-git-history v0.1.0.

The exact plugin announcement in #23574 has installation steps, screenshots, host/SDK boundaries, verification evidence and limitations.

It requires the prototype host fork, verified at 571e849048, and does not imply upstream approval. It is not available in upstream T3 Code today. Install by pasting https://github.com/digitalxero/t3-git-history into that host's Settings → Plugins, then open Settings → Extensions → Git history on the repository's environment.

This adds repository-wide topological history across branches/tags, with an explicit commit → parents table, ref context, message/author/date, changed files and parent-specific textual patches. Follow parents or navigate back from a patch to its commit. It complements T3's existing per-commit branch comparison. No checkout/rebase/fetch or destructive controls are included.

The first release uses a relationship table rather than colored graph lanes, and its portable patch view does not control the builtin diff pane. Queries are bounded/paged: 15 commits/page, 8 KiB output and 10 seconds/query, with explicit patch truncation. Real URL installation/lifecycle, installed Linux web-client navigation, ordinary packaged-worker loading and real Git fixtures were verified; plugin CI passed on Linux/macOS/Windows. Native mobile/Electron GUI, relay/tunnel runtime and SEA remain unverified. See the pinned verification receipt for the full scope and host CI disclosures.