A GitKraken-class git GUI for Linux desktop. BranchPilot wraps the system
git command-line tool directly — there is no libgit2, no native git
bindings, and no bundled git binary (except in the Flatpak, whose sandbox
cannot run the system's git). Authentication stays exactly where it
already lives: your system's git credential helpers and ssh-agent. The app
never sees, stores, or asks for a password — it just shells out to git the
same way a terminal would.
Documentation: step-by-step guides at learn.dhivalabs.com: install · beginner guide · troubleshooting. New to the topic? Try the Git and version control learning track.
Built with Flutter (Linux desktop target) and Riverpod for state management.
None yet — this machine builds and tests BranchPilot headlessly (GNOME
Wayland here blocks the screenshot APIs a build agent would otherwise use),
so no real window capture exists to show honestly. Screenshots will be added
once the app has had a first real interactive run. In the meantime, flutter test integration_test/*.dart -d linux is the actual proof the UI works —
every flow below is driven end-to-end against a real windowed build.
Repository tabs & live status — open several repositories at once in
tabs; each tracks its own working-tree status (git status --porcelain=v2)
and refreshes automatically when files change on disk, a commit lands, or a
ref moves, via a debounced filesystem watch on the worktree and .git.
Commit graph — a lane-based visual history (git log --all --date-order), rendered with persistent per-branch lanes, curved merge/fork
edges, hollow rings for merge commits, and colour-coded ref chips for
branches, tags, remotes, and HEAD. Loads 500 commits at a time with
load-more on scroll.
Hunk-level diff staging — a unified-diff viewer with syntax highlighting. Stage or unstage a whole file, or an individual hunk, straight from the diff view; untracked files show as new-file diffs. Renamed files are handled correctly on both the stage and unstage paths.
Commit & amend — a subject/body editor with a 72-column guide, an amend toggle that prefills the previous commit message, and a commit button gated on there being something to commit. The commit-detail pane shows any graph node's full metadata, stat summary, and per-file diffs.
Branches, merge & stash — create/checkout/rename/delete branches (unmerged deletes require a confirmed force), see ahead/behind counts against upstream, merge one branch into another with in-app conflict resolution (take-ours/take-theirs/mark-resolved, then continue or abort). Stash push (with an optional message and include-untracked), list, preview as a diff, apply, pop, or drop.
Remotes — fetch, pull, and push with real streaming progress in a task
strip (not a spinner — the actual git output as it arrives). Pushing a
branch with no upstream sets one automatically; force-push requires typing
the branch name to confirm, since it rewrites the remote.
Interactive rebase — pick a base commit from the graph and get a
drag-to-reorder todo list with a per-row action (pick / reword / squash /
fixup / drop). Runs as a real git rebase -i under the hood (via
GIT_SEQUENCE_EDITOR/GIT_EDITOR helper scripts, not a re-implementation of
rebase), so a conflict pause behaves exactly like the CLI: resolve, then
continue, skip, or abort from the same conflict UI merge uses. Reopening a
repository mid-rebase resumes the UI state correctly.
Tags, cherry-pick, revert, reset, worktrees, file history — create annotated or lightweight tags (and push them individually); cherry-pick or revert any commit with the same conflict flow as merge/rebase; reset soft/mixed/hard from any graph node (hard reset requires typing the branch name); list, add, and remove worktrees; view a file's full commit history (following renames) with inline diffs.
| Shortcut | Action |
|---|---|
Space |
Stage/unstage the file currently selected in the diff view |
Ctrl+Enter |
Commit (or amend) — same as clicking the commit box's button, works even while the cursor is in the subject/body field |
F5 |
Fetch all remotes — same as clicking the header's Fetch button |
Space is ignored while a text field (e.g. the commit subject/body) has
focus, so typing a literal space never gets hijacked into staging a file.
Requires the Flutter SDK with the Linux desktop target enabled.
flutter pub get
flutter build linux --releaseThe built app is at build/linux/x64/release/bundle/branch_pilot, or under
build/linux/arm64/ when you build on an arm64 machine.
sudo snap install branchpilotThe Store listing is amd64 until an arm64 build is uploaded. On arm64, install
the .deb below, or build the snap yourself (see
packaging/SNAP.md).
The snap is strictly confined, which has two consequences worth knowing before you hit them:
sudo snap connect branchpilot:ssh-keys # required for SSH remotesA confined application cannot read hidden files at the top of your home
directory, so your ~/.gitconfig is not visible to it. Set your identity
per repository (git config user.name / user.email) — the commit box
writes repository-local configuration, so committing from the app works
without any global setup. Repositories themselves are fully accessible;
only top-level dotfiles are not.
If you want the app to use your global git configuration, credential
helpers and ssh-agent exactly as your shell does, install the .deb
below instead — it is unconfined.
sudo dpkg -i branchpilot_1.0.0_amd64.deb # Intel / AMD (x64)
sudo dpkg -i branchpilot_1.0.0_arm64.deb # ARM (arm64)Both are attached to the
release. Pick the one
that matches dpkg --print-architecture.
This installs the app under /usr/lib/branchpilot, a thin launcher at
/usr/bin/branchpilot, a .desktop entry, and hicolor icons at the
standard sizes. Launch it as branchpilot from a terminal or from your
desktop environment's application menu.
To build the package yourself from a clean checkout:
flutter build linux --release
python3 tool/make_icon.py # generates assets/icon/branchpilot_<size>.png
packaging/build_deb.sh # writes dist/branchpilot_<version>_<arch>.debThe package is built for the architecture of the machine it runs on: amd64
on an x64 machine and arm64 on an arm64 one.
CI builds these from the same release build as the .deb, for x64
(x86_64) and arm64 (aarch64), and attaches them to releases from the next
release on. They are built on Ubuntu 24.04, so they need a distribution at
least that new (glibc 2.39): Fedora 40 or later, RHEL/Rocky/Alma 10, openSUSE
Tumbleweed, current Arch Linux. openSUSE Leap 15 and RHEL 9 are too old. The
.rpm declares the glibc version it needs, so dnf and zypper refuse a system
that is too old instead of installing an app that cannot start.
Fedora, RHEL, Rocky, Alma (.rpm; dnf installs git and GTK 3 with it):
sudo dnf install ./branchpilot-1.0.0-1.x86_64.rpm # or .aarch64.rpmopenSUSE Tumbleweed (the same .rpm; it is not signed):
sudo zypper install --allow-unsigned-rpm ./branchpilot-1.0.0-1.x86_64.rpmArch Linux, Manjaro, EndeavourOS (.pkg.tar.zst; depends on gtk3 and
git):
sudo pacman -U ./branchpilot-1.0.0-1-x86_64.pkg.tar.zst # or -aarch64Each release also carries branchpilot-bin-<version>-aur.tar.gz, the
PKGBUILD and .SRCINFO of an AUR branchpilot-bin package that repackages the
release .deb. It is not on the AUR yet.
AppImage (any glibc distribution with GTK 3; it runs your system's
git, so install git first):
chmod +x BranchPilot-1.0.0-x86_64.AppImage # or -aarch64
./BranchPilot-1.0.0-x86_64.AppImageFlatpak (the GNOME 51 runtime comes from Flathub):
flatpak remote-add --user --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo
flatpak install --user ./branchpilot-1.0.0-x86_64.flatpak # or -aarch64
flatpak run com.dhivalabs.branch_pilotThe Flatpak runs sandboxed with its own git (built from the upstream
release), access to your home directory, the network and your ssh-agent.
That git reads ~/.gitconfig and ~/.config/git, but credential helpers
installed on the host are not inside the sandbox, and repositories outside
your home directory are not visible to it. See
packaging/flatpak/README.md.
Every git invocation goes through a single chokepoint, lib/git/git_cli.dart
(GitCli): git --no-pager -c color.ui=false -C <repo> ..., with a
sanitized environment and NUL-separated (-z) output wherever git supports
it. Nothing else in the app calls Process for git directly. Output
parsing (git log, git status --porcelain=v2, unified diffs, for-each-ref,
...) lives in lib/git/parsers/ as pure functions with no dart:io
dependency, which is where most of the test suite's weight sits. State is
Riverpod: a per-repository status provider drives a filesystem watcher and
cascades to everything else (branches, tags, stashes, worktrees, remote
branches, the commit graph) automatically whenever it refreshes — there is
no separate cache-invalidation layer to keep in sync by hand.
There is no libgit2, no git2dart, and no vendored git binary: BranchPilot is
purely a UI and orchestration layer over whatever git is already installed
on the system. The Flatpak is the one exception: a sandboxed app
cannot run the host's git, so the bundle carries git built from the upstream
release.
Dhiva Labs is an independent, self-funded lab. Sponsorships help bring this project and the rest of Dhiva Labs to every platform, iPhone and Mac included.
Monthly sponsors at $10 and up are listed here:
Be the first: sponsor Dhiva Labs.