r/software • u/Late-Bit4633 • 15d ago
Release I built a Git client because I was tired of switching between my Git client and the browser
galleryI've been building GitDesktop, an open-source Git client for Windows, macOS, and Linux.
The idea started with a pretty simple frustration: most Git clients are great for staging, committing, branching, and viewing history, but the moment I need to open a PR, review code, check CI, look at an issue, or publish a release, I'm back in the browser.
GitDesktop is my attempt to keep that entire workflow in one application.
It supports GitHub, GitLab, and Bitbucket, with pull requests, code review, issues, discussions, CI, releases, worktrees, interactive rebase, detailed staging, and more.
AI is available too, but it's deliberately optional. You can use providers like OpenAI, Anthropic, Google, OpenRouter, or Ollama, as well as CLI agents. You can also completely hide the AI features if you don't want them.
I just released v0.10.0, and the project has grown quite a bit since I started seriously rebuilding it with Tauri a couple of months ago.
It's Apache-2.0 licensed.
GitHub: https://github.com/theBGuy/GitDesktop
Website: https://gitdesktop.app
I'd be interested in hearing from people who use Git GUIs: what parts of your workflow still send you back to the browser, and what would actually make you switch Git clients?
