Multi-repo control
See dirty, ahead, behind, clean, and conflicted repositories together.
Git work without the tab sprawl
A native multi-repository Git workspace for Windows and macOS, built for the work between a single commit and an entire engineering portfolio.
Version 2.0.0 Windows 10/11 macOS 12+
Built around repositories
Scan repositories, compare state, resolve conflicts, review history, automate repeat work, and connect the tools your team already uses.
See dirty, ahead, behind, clean, and conflicted repositories together.
Commit, branch, stash, sync, inspect, and recover without losing command-level control.
Connect supported providers or local models while keeping credentials in the operating system vault.
Build repeatable workflows and protect repositories across local and cloud destinations.
First-party add-on
A focused coding workspace that plugs into LGI through the signed extension runtime. It launches only after the runtime, entitlement checks, and release gates are complete.
$19.00
Available only after the release gate passes.
For extension developers
Developers will publish signed LGI add-ons through a reviewed directory, documented APIs, scoped permissions, and reproducible package checks.
Use the versioned SDK and manifest contract.
Provide reviewable source, provenance, and a reproducible build.
Automated scanning and human review verify permissions and behavior.
Signed packages reach users through the LGI directory.
Community supported
LGI remains free to download. Donations support signing, infrastructure, testing, and continued development.
Sign in so recurring support can be managed securely and reflected in Let's Git It.
Sign in to support monthlyYes. The core Windows and macOS application is free. Optional add-ons may be sold separately.
Submitted source is restricted to the review pipeline and authorized reviewers. Published packages are signed and traceable to reviewed source.
Directory submissions must remain reviewable and reproducible. Obfuscated third-party source is rejected because obscurity cannot replace verification.