Git work without the tab sprawl

Let's Git It

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

One workspace for the whole Git day

Scan repositories, compare state, resolve conflicts, review history, automate repeat work, and connect the tools your team already uses.

01

Multi-repo control

See dirty, ahead, behind, clean, and conflicted repositories together.

02

Native Git operations

Commit, branch, stash, sync, inspect, and recover without losing command-level control.

03

Bring your own AI

Connect supported providers or local models while keeping credentials in the operating system vault.

04

Automation and backup

Build repeatable workflows and protect repositories across local and cloud destinations.

First-party add-on

Extended IDE 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.

  • Editor and language tooling
  • Git-aware coding context
  • Signed first-party extension
  • One purchase, no subscription
Join launch updates

For extension developers

Extension service coming soon

Developers will publish signed LGI add-ons through a reviewed directory, documented APIs, scoped permissions, and reproducible package checks.

  1. 1

    Build

    Use the versioned SDK and manifest contract.

  2. 2

    Submit source

    Provide reviewable source, provenance, and a reproducible build.

  3. 3

    Pass review

    Automated scanning and human review verify permissions and behavior.

  4. 4

    Publish

    Signed packages reach users through the LGI directory.

Questions, answered

Is LGI free?

Yes. The core Windows and macOS application is free. Optional add-ons may be sold separately.

Are extension submissions private?

Submitted source is restricted to the review pipeline and authorized reviewers. Published packages are signed and traceable to reviewed source.

Can extensions be obfuscated?

Directory submissions must remain reviewable and reproducible. Obfuscated third-party source is rejected because obscurity cannot replace verification.