git-explain-tui — ask your Git history
Get started ↓
Git history, finally conversational
Stop guessing why<br>the code changed.
Browse branches, commits, files, and colorized diffs in one terminal<br>view. Then ask the selected change what it does, why it exists, and<br>where it might break.
Start exploring ↓<br>Read the docs →<br>View the code ↗
4 context modes<br>5 focused panes<br>∞ better questions
01 · Branches<br>02 · Commits<br>03 · Files<br>04 · Diff<br>05 · Chat
01 choose a branch02 find a commit<br>03 focus a file04 inspect the diff<br>05 ask with that exact context
See it in action
A quick tour of the investigation loop.
Browse a branch, focus a commit and file, then ask an AI model about the exact change on screen.
Watch the terminal demo ↗
The problem
Every repository has a<br>second codebase: its history.
Commit messages are often too short. Diffs are too large. And copying both into a generic chat window loses the thread every time.<br>git-explain-tui keeps the evidence, the question, and the answer in one place.
A better investigation loop
From “what is this?” to<br>“I can own this.”
01
Find the moment
Switch branches, filter commit history, and move through focused changes without leaving your terminal.
02
Control the evidence
Ask about the full patch, a selected file, a concise summary, or a branch range. Big changes stay manageable.
03
Keep asking better questions
Chats remain scoped to the selected commit, file, or range, so follow-up questions retain their evidence and history.
Focused context
The diff you need.<br>Not the repository you don’t.
Move from a whole commit to one changed file in a keystroke. Search diffs, filter commits, and make every prompt deliberate.
Mode: file · Context: ~3,428 chars
Built for review
Turn a diff into a review plan.
One-key actions summarize the change, surface risks, suggest tests, explain a bug fix, or draft a PR note.
sRtbp
History that stays useful
Come back to the answer.
Chats are saved per repository and commit. Copy or export the result when it belongs in a review, issue, or release note.
.git/git-explain-tui/chats/
Pricing
Free to use.<br>Free as in beer.
There is no paid tier, feature gate, or git-explain-tui subscription.
diff --git free/pricing pro/pricing
@@ plans @@
Free$0
Pro$19/month
Prostill $0
Your chosen model provider may charge for its API; local models remain local.
“A terminal-first tool for the question every unfamiliar commit creates:”
Why did someone do this?
Get started
Make your next<br>codebase less mysterious.
Works on macOS and Linux with Git. The standalone path needs no Python; PyPI options need Python 3.10+. Add a model key only when you want chat.
Install standaloneno Python
# macOS / Linux: download the right release binary<br>curl -fsSL https://raw.githubusercontent.com/mmcs-work/git-explain-tui/main/install.sh | sh
# inside any Git repository<br>git-explain-tui<br>Copy install
Install from PyPIwith uv
# isolated Python tool installation<br>uv tool install git-explain-tui
# inside any Git repository<br>git-explain-tui<br>Copy uv install
Another PyPI optionwith pipx
# if pipx is already installed<br>pipx install git-explain-tui
# then, inside any Git repository<br>git-explain-tui<br>Copy pipx install
Developing or need unreleased changes? uv tool install git+https://github.com/mmcs-work/git-explain-tui.git. The README also covers virtual-environment installation.