[ overgit ] · a git client
Stage, commit, read the graph and push — fast, with the keyboard. And when a ticket touches several repos, a workset branches, commits and pushes them together, tells you before you push whether it all lands — and follows them through review: every pull request’s CI and approval in one place, each linked to the others.
[ the basics ] · everything you'd expect
Before worksets and Landing Check, it has to be a git client you would pick anyway — so the everyday work is fast, keyboard-first and plain git underneath.
[ worksets ] · a ticket across repos
A workset is the work in flight: the repos a ticket touches, pinned to one branch. Come back to it after other work and overgit sees which repos drifted — Resume puts every one back on the branch, and stops to ask about anything dirty.
[ everyday ]
⌘K runs anything — switch a branch, jump to a repo or workset, push the whole workset. ⌘B is a branch picker that can sync, pull and branch in one go.
[ ai ]
Review with AI pipes the diff to claude, codex or gemini on your own login. Suggest drafts the commit message from what you staged. overgit itself sends nothing anywhere — reviews run through your own claude, codex or gemini login.
Robin and robin get separate buckets. Lower-case it first.✨ Suggest with claude · drafts the message from the staged diff[ safety ]
Reset all fetches, switches and pulls every repo in a workspace. A repo with commits that would be lost stops and asks — force it, or skip it.
[ download ] · grab a build
Overgit is in beta, and from v0.3.0 the macOS builds are Developer-ID signed and notarized by Apple, with the same Developer ID as overcli. They open on a double-click. Windows isn't code-signed yet, so SmartScreen may still flag it. From v0.4.2 it updates itself from GitHub Releases, so this is the last download you do by hand. Either way, the source is right there if you'd rather build it yourself.
Stable macOS builds open clean — signed with a Developer ID and notarized by Apple, so there's no Gatekeeper prompt. Windows isn't code-signed yet: SmartScreen may say “unrecognized app” → More info → Run anyway. Rather build it yourself?git clone https://github.com/overcodelions/overgit && cd overgit && npm install && npm run dist:mac
[ faq ]
Nothing. Overgit is free and open source under Apache 2.0 — no licence to buy, no per-seat pricing, no paid tier holding features back. There is no account to create and no server to pay for: it is a desktop app driving the git you already have.
It keeps none of its own data inside .git. Workspaces and worksets live in overgit's own state; everything it does to a repo runs as the plain git commands you'd have typed yourself.
Uninstall it and your repos forget it ever existed — same branches, same remotes, same config. There is no migration to undo and nothing to export, because nothing was ever stored in the repo.
A workspace is a durable grouping of repos — "these are Platform," "these are Payments" — the lens you fetch, status, and reset across. A workset is a ticket you can resume across those repos, pinned to a feature branch: spin up, ship, archive, reset.
Every destructive flow shows you exactly what it is about to discard, per repo, before it runs. That check is the reason the feature exists.
If it speaks git, yes — overgit doesn't care who hosts it. On top of that, cloning can browse GitHub, GitLab and Bitbucket directly, and pull request aggregation goes through the gh CLI. All of it rides on credentials already on the machine — your gh or glab login, or your git credential helper. Overgit never asks for, stores, or transmits a token of its own.
Yes — Apache 2.0, and the repo builds from source. There is no server component to review: it is a desktop app driving local git.
[ family ] · over your tools, not instead of them
One window over your agent CLIs — then put them in a loop.
A better git client — and one ticket across many repos.
Every environment at once — and branches of your data.
overgo →overcli for your whole team — on your own server.