For years I’ve used SmartGit at work. I like its multi-pane workflow: repositories, files, history graph and diff, all on one screen. But it’s free only for non-commercial use, and I wanted something I could use anywhere, change when I needed, and share with others.
So I started WinGit, an open-source Git client for Windows.
What it does today
- Repository status, staging and committing
- Push / pull / fetch
- Commit history
- Setting custom author/committer dates for a commit (I needed this myself – e.g. for fixing wrong clocks or time zones)
It covers my everyday needs, but it’s still early: expect rough edges.
Why Java and Swing in 2026?
I’m a Java developer, and modern Swing with FlatLaf looks surprisingly good – IntelliJ IDEA is proof of that. A few technical decisions:
- JGit for reads, native git CLI for writes. Starting a process on Windows costs tens of milliseconds, so frequent reads go through JGit, while commits, push/pull and hooks go through the real git. That keeps it fast and fully compatible.
- No Git work on the UI thread. Everything runs in the background and results are published back to Swing.
- jpackage builds a Windows installer with an embedded runtime, so you don’t need Java installed.
Built with AI assistance
I develop WinGit with Claude Code as a coding assistant. It speeds things up a lot, but architecture, review and testing are on me. I’ll probably write a separate post about that experience.
I’m looking for beta testers
If you use Git on Windows, I’d love your feedback:
- Download the latest release: https://github.com/biblelamp/WinGit/releases
- Try it on a real repository (a copy or one with a remote, just in case)
- Tell me where you got stuck or what you miss compared to your current client
Issues, ideas and stars are all welcome: https://github.com/biblelamp/WinGit
Thanks for reading! What Git client do you use on Windows, and what annoys you the most about it?

Top comments (0)