Active development macOS (Apple Silicon) · Linux x64 · Windows x64

Your whole repo, in one window.

The graph, pull and merge requests, CI, issues, releases, terminals, AI runs, your .http requests and a file editor — in the same app, so shipping a change stops being a tour of four of them.

Download BeardGit See what it does Star on GitHub

If it saves you a tab, a ★ on the repo is how other people find it.

100K+
Commits it renders
31
Themes built in
2
Forges, both first-class
0
Accounts to create
§ 01 — Why it exists
I kept the graph in one app, the merge request in a browser tab, the pipeline in another, and the API call I wanted to test in a fourth. None of those tools was bad. The jumping was. So BeardGit puts the things I touch to ship a change in one window, in a shape I can keep in my head. It is not out to be the last Git client you install — plenty of them are older, bigger and better funded. It is the one where the next step is usually already on screen.

Six views, one window.

§ 02 — A look at it

Another fourteen views — branches, tags, stashes, worktrees, submodules, reflog, bisect, issues, releases, pipelines, compare — are on the features page.

Pick a theme. The whole app follows.

§ 03 — Themes

Three original families — BeardGit (copper, the default), Fjord and Nebula — plus the classics you already use elsewhere, for 31 built-in themes. It isn't only chrome: the editor's syntax colours, the diff backgrounds and the graph lanes recolour with it. Your own theme is a TOML file with 18 colours; everything else is derived for you. This page follows too — flip the toggle up top.

+ Rosé Pine · Everforest · Kanagawa · Ayu · Catppuccin · Dracula · Gruvbox · Nord · Tokyo Night · Solarized · Oxocarbon …
The in-app file editor rendered in the selected theme
the editor in BeardGit

What you get, briefly.

§ 04 — What you get
01 / 06

A graph drawn on canvas.

Six-figure histories scroll smoothly, because only the rows on screen are drawn. Lanes, merge curves, ref badges, author highlighting, and a search that re-lays out around the matches.

02 / 06

GitHub and GitLab, both properly.

Pull requests and merge requests with per-file diffs and inline review threads. Issues, labels, milestones, pipelines, releases, repo settings. Self-hosted instances included.

03 / 06

Staging down to the line.

Collapse a hunk, expand the whole file, stage or discard single lines, Shift-select a range. Commits honour your signing config, and a Test signing button shows the real error when it fails.

04 / 06

AI runs in a worktree, not in your tree.

Your own install of Claude Code, Codex or OpenCode, started on its own ai/<provider>/<slug> branch in an isolated worktree. Read the transcript, then merge or throw it away. Your checkout never moves.

05 / 06

Requests and an editor, in the repo.

Plain .http files under .beardgit/requests/, committed with the code that calls them. And a CodeMirror editor for quick fixes: save writes to disk, Shift-save also stages it.

06 / 06

Real terminals, and a command palette.

xterm.js over a native PTY, with the bundled gh and glab on hand. ⌘⇧P reaches every view and every shortcut without a menu hunt.

The long version, view by view, is on the features page. How to actually use each one is in the guide.

Whether it fits you.

§ 05 — Whether it fits

You'll probably like it if you

  • work on GitHub or GitLab — or both, on different repos, on the same afternoon
  • test APIs against the repo you are looking at, and would rather not open a separate API client
  • run Claude Code, Codex or OpenCode and want them in a worktree instead of loose in your checkout
  • prefer a native app to another Chromium runtime
  • use Linux and are tired of being the afterthought platform

You probably won't if you

  • are happy in git and lazygit — this is a GUI, and it won't beat your muscle memory
  • need SVN, Mercurial, Perforce or Bitbucket — none of them are supported
  • want a signed installer today, an SLA, or a support line — it's one developer and an unsigned build
  • are on an Intel Mac — only Apple Silicon builds are published

Free, and the source is right there. The CC BY-NC-SA licence stops someone reselling BeardGit itself; using it at work, on work code, is fine.

The rough edges, up front.

§ 06 — Rough edges

Better said here than discovered on your own machine. None of these are secrets — they are in the changelog and the issue tracker too.

The builds aren't signed

macOS and Windows both block the first launch. One command on macOS, two clicks on Windows, once per install. Certificates cost money per year and this is a one-person project; it is on the list.

Three platforms, three formats, no more

.dmg for Apple Silicon, .AppImage for Linux x64, .exe for Windows x64. No Intel Mac build, no .deb, .rpm or .msi. Building from source covers the rest.

Two forges, not five

GitHub and GitLab are first-class, self-hosted included. Bitbucket, Gitea and Codeberg are not supported: the provider layer is abstracted, but each one still needs a real driver and tests behind it.

It needs git on your PATH

Reads go through libgit2, writes shell out to your own git. The app doesn't check for it at startup, so if it's missing you'll find out when a commit fails rather than when you launch.

One request per .http file, for now

The parser understands several blocks in a file; the panel still runs the first one. It also won't reach localhost unless you opt in — see the guide.

One developer, in the open

Bugs get fixed when they're reported, and the changelog says which and why. If you need a maintained-by-committee product, that's fair — Fork, Tower, GitKraken and lazygit are all good, and none of them owe me anything.

Download, approve once, launch.

§ 07 — Install

The installers are unsigned, so your OS stops the first launch. Approve it once and it runs like any native app. gh and glab come bundled, so there is nothing else to install.

macOS
Apple Silicon · .dmg
Download for macOS ↗
xattr -dr com.apple.quarantine /Applications/BeardGit.app
Drag it to /Applications, then run that command once to clear Gatekeeper's quarantine flag. It goes away when the app is signed.
Linux
x64 · .AppImage
Download for Linux ↗
chmod +x BeardGit-*.AppImage && ./BeardGit-*.AppImage
Mark it executable and run it. Needs libwebkit2gtk-4.1. No .deb or .rpm right now — build from source if you need one.
Windows
x64 · .exe
Download for Windows ↗
SmartScreen → More info → Run anyway
Needs the WebView2 Runtime, which Windows 11 already has. The .msi comes back once the app is signed.
§ 07.1 — From source

Rather build it yourself?

Rust, Node 22 and Tauri 2. The prerequisites per platform and the exact commands are in the guide. Licensed CC BY-NC-SA 4.0.

Clone the repo

Common questions.

§ 08 — Questions
Is it really free? What's the catch?
Free to download and use, no account, no paywall, no telemetry. The licence is CC BY-NC-SA 4.0, which only stops someone repackaging and selling BeardGit itself. Using it to earn a living with your own code is exactly what it's for.
Why does my OS say it's damaged or unverified?
Because the builds are unsigned, not because anything is wrong with the download. On macOS run xattr -dr com.apple.quarantine /Applications/BeardGit.app once, or right-click the app and choose Open. On Windows, More info → Run anyway. Details in the guide.
Where do my tokens and AI keys live?
BeardGit doesn't manage AI keys at all — it drives your local claude, codex or opencode, which already have their own auth. Forge tokens are encrypted with AES-256-GCM in a file on your machine, under a key derived from a machine identifier. The guide says exactly where, and what that does and doesn't protect against.
Does it phone home?
There is no telemetry and no analytics in the app. On its own it makes one request: the update check, which has a switch. Turning off the GitHub/GitLab and AI integrations in Settings stops the token validation and CLI probing at launch too, leaving a git-only client. Everything else happens because you clicked something.
How does it compare to GitKraken, Fork, Sourcetree or Tower?
They're mature products with teams behind them and BeardGit isn't trying to out-do them at being themselves. The difference is what's in the same window: AI runs in worktrees, an in-repo .http workspace, and a file editor next to the graph — plus GitLab treated as well as GitHub. If that isn't what you're missing, they're a better buy.
Does it work offline?
Git is local, so the graph, branches, staging, commits, terminals and local AI runs all work with no network. Pull requests, merge requests, pipelines and releases obviously need connectivity, and say so instead of hanging.
How do I report a bug?
Open an issue with your OS, the version from Help → About, and what you did. If you're not sure whether it's a bug or a limitation, open it anyway — sorting that out is my job, not yours.

Longer answers, and the ones that need commands, are in the guide.