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

Your whole repo, in one window.

Graph, PRs & MRs, CI/CD, issues, releases, terminals, AI agents, an in-repo .http workspace, and an in-app editor — in one native app, themed end to end.

Download BeardGit Star on GitHub

If BeardGit saves you a tab, drop a ★ — it’s how the project gets seen.

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. Graph. Branches. Staging. PRs & MRs on GitHub and GitLab. CI. Issues. Releases. Terminals. AI agents. Your API requests, committed next to the code. Your repo files, edited in place. Close the other clients — BeardGit is the one window you keep open.

The whole repo, one window.

§ 02 — Interface

BeardGit main window — the canvas commit graph with branch lanes, merge curves, ref badges and version tags in a single tab — fig. 01 — commit graph

In-app code editor — gitignore-aware file tree and a tabbed CodeMirror buffer with theme-matched Rust syntax highlighting — fig. 02 — in-app editor

Pull request detail — rendered description, labels, reviewers, changed files and an inline review thread — fig. 03 — pull request detail

CI pipelines list with per-run status badges, plus the stages and jobs of the selected run — fig. 04 — CI pipelines

Command palette overlay — fuzzy-matched navigation views and keyboard shortcuts, opened with Cmd-Shift-P — fig. 05 — command palette

Requests panel — .http file editor with JSON body, env switcher, and a syntax-highlighted response — fig. 06 — requests panel

Issue list with labels and state, plus the selected issue body and comment thread — fig. 07 — issues

Releases list with semver tags, publish dates and asset counts — fig. 08 — releases

Branch list with upstream tracking and ahead/behind counts — fig. 09 — branches

Worktrees — the main checkout plus AI and feature worktrees on their own branches — fig. 10 — worktrees

Visual bisect mid-session — good/bad/skip controls, counters and the bisect log — fig. 11 — visual bisect

AI session transcripts from Claude Code and Codex, scoped to the repo — fig. 12 — AI sessions

The same merge-request workflow on GitLab — detail, files and review thread — fig. 13 — GitLab merge request

Pick a theme. The whole app follows.

§ 03 — Themes

BeardGit ships its own theme families — not a reskinned GitHub. The default copper identity, plus Fjord and Nebula, each with a dark and a light variant wired for OS auto-switching. And it isn't just chrome: editors and diffs follow the active theme too — syntax palette, diff backgrounds, and graph lanes all recolour together. This page does the same — flip the toggle up top.

+ Dracula · Gruvbox · Nord · Tokyo Night · Catppuccin · Solarized …

The in-app editor rendered in the selected theme — fig. 14 — the editor in BeardGit · click a theme, flip the toggle for dark/light

Everything you do, in one place.

§ 04 — Capabilities

01 / 09

A canvas graph that scales.

100K+ commits render smoothly. Branch lanes, merge curves, sync-state lines, and author highlighting — all on HTML canvas, not DOM. ⌘F filters by author, message, or ref.

02 / 09

Multi-repo tabs.

Every repo is a tab. Heavy state loads only for the active one — a dozen open repos cost the same as one. ⌘1…⌘9 jumps between them.

03 / 09

Forge-native for GitHub + GitLab.

Full PR/MR lifecycle with inline review threads. Issues, pipelines, releases, repo settings — without leaving the app. Self-hosted GitHub Enterprise and on-prem GitLab too. gh and glab bundled.

04 / 09

Your own AI CLI, in a worktree.

BeardGit drives your local install of Claude Code, Codex, or OpenCode in a fresh worktree. Each run lands on its own ai/<provider>/<slug> branch — review, merge, or discard.

05 / 09

Visual bisect.

Pick the good commit, pick the bad commit, step through with buttons. Auto-mode runs your test command at every step and resolves it without you watching.

06 / 09

Bundled CLIs.

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

07 / 09

An in-app code editor.

CodeMirror 6 with per-language snippets, keyword completion, JSON lint, inline color pickers, and a gitignore-aware tree. Save writes to disk; ⇧ Save also stages for the next commit.

08 / 09

An .http workspace, in your repo.

Plain .http files in your repo, committed with the project. Envs in JSON, secrets encrypted locally. Response diff between any two runs.

09 / 09

A command palette for everything.

⌘⇧P fuzzy-matches every view and every keyboard action — type stash, hit Enter, you're there. No menu hunting.

Made for the dev with six tabs open.

§ 05 — Who it's for

Five minutes from download to first commit. No accounts, no cloud. A deliberate choice for a specific kind of developer.

You’ll like it if you

live on GitHub or GitLab and want a first-class experience on either — not “GitHub plus a GitLab bolt-on”
test APIs against the repo you’re staring at and hate context-switching to a separate API client
run Claude Code / Codex / OpenCode and want them isolated in worktrees, not loose in your tree
care that your git client doesn’t ship a 200 MB Chromium runtime to render a sidebar
want a polished GUI with Linux as a first-class platform, not an afterthought

You probably won’t if you

live entirely on git CLI and lazygit — BeardGit is GUI-first
need SVN, Mercurial, Perforce, or self-hosted Bitbucket — not supported
want a paid product with phone support and an enterprise SSO portal — that’s not this

Free and source-available. CC BY-NC-SA blocks reselling BeardGit itself; commercial team use is fine.

Twelve keys, no menus.

§ 06 — 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⌘⇧K
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
Command palette⌘⇧P
Show all shortcuts?

Download, approve, launch.

§ 07 — Getting started

Builds are unsigned, so your OS blocks the first launch. Approve the app once and it runs native. gh and glab ship bundled. Code-signing is on the roadmap.

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.

§ 07.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.

§ 08 — FAQ

Why is the app unsigned?

Signing certificates cost real money per year and BeardGit is a one-person beta. Until that changes, your OS will block first launch — the workaround in § 06 is one 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. Your tokens never touch BeardGit's storage.

Why no Electron?

Electron ships a Chromium runtime per app — ~150 MB before you do anything. BeardGit is built on Tauri 2 and uses the OS's native webview. Small installer, fast cold start.

Can I theme it? Does it match my editor?

Yes. BeardGit ships three original theme families — BeardGit (copper, the default), Fjord and Nebula — each with dark and light variants that follow your OS automatically, alongside the usual Dracula / Gruvbox / Nord / Tokyo Night / Catppuccin / Solarized pairs. Crucially the theme drives the whole app: the in-app editor's syntax palette, diff backgrounds and the graph lanes all recolour with it, so nothing reads as a bolted-on GitHub skin.

How does it compare to GitKraken / Fork / Sourcetree / Tower?

BeardGit isn’t trying to beat any of them at being themselves — they’re mature commercial products. BeardGit is the opinionated alternative for developers who want AI worktree runs, an in-repo .http workspace, and an in-app editor in the same window as the graph. See § 04 — Who it’s for.

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 and use, no account, no telemetry, no paywall. CC BY-NC-SA 4.0 only forbids repackaging or reselling BeardGit itself — using it to earn money with your code is fine.

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.