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

Your whole repo, in one window.

Graph, branches, staging, PRs & MRs, issues, CI/CD pipelines, releases, terminals, and AI agents — in a single native app. Stop jumping between GitHub, GitLab, the terminal, and three other clients just to ship a commit.

Download BeardGit Read the source
100K+
Commits rendered
0×
Electron runtimes
3 AI
Providers built-in
§ 01 — Manifesto
You ship code from one keyboard, not seventeen tabs. BeardGit is built on a simple premise: everything you touch to release a change should live in one app. Your commit graph. Your branches. Your staging. Your pull requests and merge requests on GitHub and GitLab. Your CI pipelines and deploy jobs. Your issues, labels, and releases. Your terminals. Your AI agents. Close the browser tabs. Close the other clients. BeardGit is the one window you keep open.

Everything you do, in one place.

§ 02 — Capabilities
01 / 06

A canvas graph that scales.

100K+ commits render smoothly via a viewport-sliced renderer. Branch lanes, merge curves, sync-state lines, and author highlighting — all on HTML canvas, not DOM.

02 / 06

Multi-repo tabs.

Every repository is a tab. Heavy state — repo, layout, file watcher — loads only for the active tab; background tabs keep just their metadata.

03 / 06

Forge-native for GitHub + GitLab.

Create, edit, merge, approve, and comment on PRs/MRs. Manage issues, labels, milestones, assignees. Trigger and retry pipelines. Publish releases — without leaving the app. gh and glab ship bundled.

04 / 06

Your own AI CLI, in a worktree.

BeardGit drives your local install of Claude Code, Codex, or OpenCode in a fresh git worktree — no terminal, no key juggling. You keep the CLI you already configured; the app just spawns it, queues runs, and pipes the transcript back in-app. More providers will follow.

# Cmd+Shift+A — pick prompt + provider + worktree root
AiBackgroundCoordinator::queue(run) // FIFO
  .launch("claude-code", "--print --stream-json")
  .in_worktree(".beardgit/ai-worktrees/<id>")
  .cap(3) // concurrent runs
05 / 06

Visual bisect.

Pick the good commit, pick the bad commit, step through with buttons. Visual runner pairs with the bundled CLIs and the AI worktree flow — no terminal juggling.

06 / 06

Bundled CLIs.

gh and glab ship inside every installer. No PATH setup. Run them in a PTY terminal inside the app, or let BeardGit call them for you.

The whole repo, one window.

§ 03 — Interface
BeardGit main window — commit graph, branches, and diff in a single tab
fig. 01 — main window
Canvas commit graph showing branch lanes, merge curves, and author highlighting
fig. 02 — commit graph
AI background run transcript inside a worktree, with provider and prompt selection
fig. 03 — AI background run
Pull request detail with CI pipeline status and inline review comments
fig. 04 — PR / pipeline

Twelve keys, no menus.

§ 04 — Keyboard

A taste of what ships built-in. The full cheat sheet is one keystroke away — press ? inside the app. Modifiers shown for macOS; on Linux/Windows ⌘ reads as Ctrl.

Git

  • Stage all changes⌘⇧S
  • Push⌘⇧P
  • Pull⌘⇧L
  • Fetch⌘⇧F
  • New branch⌘⇧B

Graph

  • Next / previous commitJ/K
  • First / last commitHome/End
  • Search commits/
  • New AI background run⌘⇧A

Tabs & UI

  • Next tab⌘Tab
  • Close tab⌘W
  • New terminal tab⌘T
  • Toggle sidebar⌘B
  • Show all shortcuts?

Download, approve, launch.

§ 05 — Getting started

Builds are currently unsigned, so your OS will block the first launch. Grab the installer for your platform, approve the app manually once, and it runs like any other native app. The per-platform workarounds below are temporary and will go away as soon as code-signing is in place. gh and glab ship bundled — no PATH setup.

macOS
Apple Silicon · .dmg
Download for macOS ↗
xattr -dr com.apple.quarantine /Applications/BeardGit.app
Drag to /Applications, then run the command above once to clear Gatekeeper's quarantine flag. Temporary — goes away with code-signing.
Linux
x64 · .AppImage
Download for Linux ↗
chmod +x BeardGit-*.AppImage && ./BeardGit-*.AppImage
Mark executable and run directly. Requires libwebkit2gtk-4.1. .deb / .rpm bundles aren't shipped right now — build from source if you need them.
Windows
x64 · .exe
Download for Windows ↗
SmartScreen → More info → Run anyway
Requires WebView2 Runtime (installed on Windows 11 by default). The .msi bundle will return once the app is code-signed.
§ 05.1 — From source

Rather build it yourself?

Rust + Node + Tauri 2. Full setup and platform prerequisites live in the README. Licensed CC BY-NC-SA 4.0.

Clone the repo

Frequently asked.

§ 06 — FAQ
Why is the app unsigned?
Code-signing certificates for macOS and Windows cost real money per year, and BeardGit is a one-person project shipping a beta. Until that changes, every build is unsigned and your OS will block first launch. The per-platform workaround in § 05 takes a single command. Signing is on the roadmap.
Where do my AI keys live?
BeardGit doesn't manage keys. It drives your local install of claude-code, codex, or opencode, which already have their own auth in your home directory. The app spawns the CLI in a fresh worktree and pipes the transcript back — your tokens never touch BeardGit's storage.
Why no Electron?
Electron ships a Chromium runtime per app — ~150 MB of memory before you do anything. BeardGit is built on Tauri 2, which uses the OS's native webview (WebKit on macOS, WebView2 on Windows, WebKitGTK on Linux). The installer is small and the cold start is fast.
Does it work offline?
Yes — Git is local-first. Graph rendering, branches, staging, commits, terminals, and AI runs against a local CLI all work without a network. PR/MR/CI and remote pipeline triggers obviously need connectivity, and degrade cleanly when you go offline.
What about Bitbucket, Gitea, Codeberg, …?
Today only GitHub and GitLab are first-class. Bitbucket and Gitea are on the wish-list once the GH/GL surface stabilises — the forge layer is abstracted, but each backend still needs a real driver and tests. PRs welcome.
Is BeardGit really free?
Yes — free to download, free to use, no account, no telemetry, no paywall. Use it on your own machine, at work, on as many repos as you like. The licence is CC BY-NC-SA 4.0: the only thing it forbids is repackaging or reselling BeardGit itself as a commercial product, so the author keeps the right to do that down the line. Using it to earn money with your code is fine — that's the whole point.
How do I report a bug or request a feature?
Open an issue on GitHub. Include your OS, the BeardGit version (Help → About), and a short repro. Patches via PR are very welcome — see CONTRIBUTING.md.