Desktop Git client
A Git client that stays fast when the history is real.
FluxGit brings visual Git history, focused staging and review of risky operations to macOS, Windows and Linux. Follow the branches, inspect the exact changes and see the available recovery path before acting. When a compatible coding agent proposes a Git write through MCP, you decide whether it runs.
See the change before you commit
Read branches together in the graph or place commits on a timeline. Compare two commits or branches, then stage a file, a hunk or selected changes. Conflicts, stashes, tags, worktrees and submodules sit beside the history, so you can inspect repository state before choosing the next operation.
Keep agent proposals reviewable
Codex, Claude Code and OpenCode are independent coding tools. MCP compatibility depends on the host supporting a local stdio server. On that path, agents inspect and propose; FluxGit presents the operation, risk and recovery context for approval or rejection. A shell separately granted to the agent stays outside this approval boundary. The agent control guide explains supported integrations and their release scope.
Choose a recovery path before a risky action
Review the preview before reset, rebase or other history changes. Covered operations can capture Flux restore points or safety snapshots. Reflog can help locate earlier commits; its retained entries determine what is available. Discard warns when no restore point is created, so protect uncommitted work before proceeding.
The graph, measured
On 29 September 2026, 100,000 linear commits averaged 55.9393 ms for graph layout on Apple M4, macOS 26.2 and Node 24.15.0. The synthetic commits were already loaded in memory. These timings exclude Git reads, startup, network operations and canvas rendering; they do not measure opening a monorepo or Linux performance.
Full-layout rows used 22–27 samples. The incremental row reused cached history, with five samples and ±17.77% relative margin of error. The linear row used 27 samples and ±6.13%. Reproduce the source measurement from a source checkout with the command below.
| History already in memory | Mean layout time |
|---|---|
| 100,000 linear commits | 55.9393 ms |
| 100,000 commits, 512 interleaved branches | 65.4451 ms |
| 100,000 merge-heavy commits | 69.0414 ms |
| 100 added commits, 99,900 cached | 13.1805 ms |
npm --prefix app/ui run bench:graphTry one complete Git workflow
Use a disposable repository for the first risky operation and keep your usual backup for important work.
- Inspect the branch and working changes, then stage one intentional change.
- Read the preview and available recovery context before running a history operation.
- Use Git School to practise undoing a commit or recovering after reset.
Choose your desktop build
Public beta downloads cover macOS Apple Silicon and Intel, Windows x64 and Linux x86_64. macOS builds are signed and notarized. The Windows installer is not code-signed and can show SmartScreen. Linux uses a Debian/Ubuntu .deb; choose the current platform build on the download page.
Free mode opens public repositories on GitHub, GitLab.com and Bitbucket.org. Private, self-hosted and local-only repositories need a licence. A 14-day trial covers the licence features with no card; public checkout is not enabled.
Frequently asked questions
Can an agent write without approval?
Operations submitted through FluxGit MCP require a desktop decision. Commands issued through an independently available shell are outside that boundary.
Is every Git change reversible?
No. Recovery depends on the operation, captured restore points and retained Git data. Check the preview before running an action.