One developer, one focused tool
I built LetsGit because my Git GUI kept crashing on a 200k-commit repo.
The backstory
A slow work laptop, a massive fintech repo, and a GUI that couldn't keep up.
I work in fintech on a repository with over 200,000 commits. My work laptop isn't fast. Sourcetree would freeze mid-rebase, crash during log scrolls, and lose context when I needed it most. The terminal worked, but I wanted something visual that could actually handle the scale.
So I started building LetsGit — a native desktop app with a Rust backend that spawns system git, streams large diffs over localhost HTTP, and virtualizes every list. Four months in, it already handles my daily workflow without the crashes. I design, code, and ship every part of it alone.
What guides the product
Speed, safety, and clarity — in that order.
CLI-first architecture
LetsGit spawns your system git — no bundled libgit2, no surprises. The same commands you trust in the terminal power the UI.
Built for scale
Virtualized lists, chunked diffs over localhost HTTP, and SQLite caching keep the interface responsive on repos with hundreds of thousands of commits.
Safety by default
Risky actions require explicit confirmation. Recovery workflows are always one click away. No silent force-pushes.