GitCraft is a free, open-source visual Git client written in Rust that gives you a graphical view of your repositories — commit graph, branches, tags, diffs, conflict resolution and a built-in terminal — without the weight of the Electron apps that dominate this space. It is built with Rust and egui, the same stack as the ArtCraft suite, it runs on Windows, Linux and macOS, and it drives the Git command line you already have installed, so your config, credentials and hooks apply exactly as usual.
It is also very young: the repository was created on 27 October 2026, it had 69 stars and 6 forks as of 18 November 2026, and the latest release is v0.3.4, published 15 November 2026. What it already does is unusually complete for a three-week-old project — the README documents a full graph view, interactive rebasing, side-by-side diffs, a three-pane conflict editor, worktrees, stashes, pull requests and an undo system that covers almost every action. This article checks each claim against the repository itself, shows how to install it, and compares it honestly with GitKraken, Sourcetree, GitHub Desktop and lazygit.
What GitCraft actually is
GitCraft lives at github.com/Vancete/gitcraft and describes itself in one line: "A visual git client, simple to use yet powerful. Light, fast and debloated." The project is open source under the Apache License 2.0 (the repository also ships an MIT licence file), and it is written in Rust on top of egui and eframe — a native GUI toolkit, not a web view wrapped in a desktop shell. That choice is the whole point of the project: no Chromium runtime, no heavy JavaScript layer, just a small binary that starts fast and stays out of the way.
The important design decision is that GitCraft does not contain its own Git implementation. It shells out to the git command line installed on your machine. That means your global config, your credential helper, your hooks, your aliases and your signing setup all behave exactly as they do in your terminal. It also means Git must be installed before GitCraft is useful — the start page checks for it.
The interface follows the shape of the classic graph-based Git clients. Branches, remotes, worktrees, stashes and tags sit in a left sidebar. The centre holds the commit graph, with coloured lanes for each branch and small pills marking branch and tag tips. The right pane shows uncommitted changes and the commit box, and a terminal panel sits along the bottom. Tabs work like a browser: one tab per repository, with Ctrl+T and Ctrl+W, and your open tabs, recent repositories, theme and settings are remembered between sessions.
How a commit flows through GitCraft
The flow above is the normal loop, but the last line of the diagram is the feature that sets GitCraft apart from most Git GUIs: undo. Ctrl+Z and Ctrl+Y work across commits, amends, merges, rebases, pulls, resets, cherry-picks, reverts, checkouts, branch creation, renames and deletes, tags and stashes. A mistaken git reset --hard in a terminal is a recovery job; in GitCraft it is one keystroke back.
The six headline features, checked against the README
The post that put GitCraft on people's timelines lists six features. All six are real, and all six are documented in the project's README. Here is what each one actually means in the app.
1. Visual commit history. The graph shows every branch in coloured lanes, with branch and tag pills in their own column to the left of the graph, placed on each branch's tip only and joined to their commit. A pill shows a laptop icon when the branch is local, a cloud when a remote has it at that commit, and a pull-request icon when one is open. The checked-out branch's pill is solid; the others are a darker shade. Double-click a pill to check that branch or tag out. History loads 1,500 commits at a time as you scroll, and Ctrl+F searches messages, authors and hashes across all of history — or switches to Code mode to find the commits that added or removed a piece of text in a file, using git log -S. Each commit shows its summary followed by the rest of its message, faded and cut to fit, plus the author's avatar and a relative date ("2 hours ago"). An Uncommitted changes row sits on top while the working tree is dirty.
2. Branch and tag management. The left sidebar lists local branches with ahead/behind counts. Right-click a branch to check it out (or check it out in a new worktree), fast-forward it, merge it into the current branch or rebase it onto the current branch, push it, create a pull request, rename it or delete it. Remotes can be added, edited, fetched and removed, with their branches listed below each one. Tags can be created — light or annotated, optionally pushed — and deleted locally or on the remote. Right-clicking a commit offers creating a branch or a tag on it, checking it out, cherry-picking, reverting, or resetting the current branch to it (soft, mixed or hard, with confirmation).
3. Interactive rebasing. Right-click a commit and choose interactive rebase onto it, or use the same option from a branch pill. The rebase editor lists the commits to rewrite, newest on top, and lets you pick, reword (editing the message in place), squash, fix up or drop each one, and move them up and down before pressing Start rebase. Ctrl+Z undoes the whole rebase. If a rebase stops on conflicts, a banner offers Abort, and the commit box finishes it with Continue rebase. The same editor also lets you double-click a commit's summary in the right pane to edit its message in place — on the latest commit it amends, on an older one it rewrites with a rebase, setting your uncommitted changes aside and bringing them back.
4. Side-by-side code diffs. Diffs open unified or side by side, with syntax colours from bat's language set (TypeScript, TSX, Vue, TOML, SCSS, PowerShell, Dockerfile and more), the changed part of each line marked, whitespace changes optional, and images shown before and after. A strip beside the scrollbar marks where the changes are; click it to jump there. You can view only the changes or the whole file, and both the layout and the scope are remembered between sessions. Version 0.3.4 improved this further: each half of a side-by-side view now takes exactly half of the visible width, so a long line no longer pushes the new side out of view. You can drag over lines to select text and copy it, and code takes the colours of the theme VS Code is using, read from its settings — a setting turns that off.
5. Merge conflict resolution. Conflicts open in a three-pane editor: each conflict's two sides with Ours, Theirs and Both buttons, and the result below, editable. For a whole file, Use mine and Use theirs settle it in one click. A merge, rebase, cherry-pick or revert that stops on conflicts shows a banner with Abort, and the commit box finishes the operation. The changes pane also lists conflicted, unstaged and staged files separately, with stage, unstage, discard and mark-resolved buttons.
6. Built-in terminal. The terminal panel has tabs and runs your real shells — PowerShell, cmd, Git Bash or WSL on Windows, your shells elsewhere — inside a real pseudo-terminal (ConPTY on Windows) with colours, scrollback, mouse selection and copy. It opens in the repository's folder, and you can open a terminal in a worktree from the sidebar. The toolbar also carries undo, redo, fetch, pull and push (with incoming and outgoing counts), new branch, stash, terminal, search, open-folder and refresh.
Features at a glance
| Area | What GitCraft does | Where it lives |
|---|---|---|
| Commit graph | Coloured lanes, branch/tag pills, avatars, relative dates, 1,500 commits per scroll load | Centre pane |
| Search | Messages, authors, hashes; Code mode finds commits by text added or removed (git log -S) | Ctrl+F |
| Branches | Checkout, fast-forward, merge, rebase, push, rename, delete, pull-request creation | Left sidebar + graph pills |
| Tags | Create light or annotated, push, delete locally or on the remote | Left sidebar + commit menu |
| Interactive rebase | Pick, reword, squash, fix up, drop, reorder; undo with Ctrl+Z | Commit menu / branch menu |
| Staging | Stage/unstage/discard whole files, hunks, or selected lines; discard is undoable | Right pane |
| Diffs | Unified or side by side, syntax colours, whole file or changes only, image before/after | Centre pane |
| Conflicts | Three-pane editor (Ours / Theirs / Both), editable result, whole-file Use mine / Use theirs | Centre pane |
| Worktrees | Add, open in a tab, open a terminal there, lock, remove, prune | Left sidebar |
| Stashes | Stash with a message (untracked files included), view contents, apply, pop, drop | Left sidebar + graph (v0.3.4) |
| Pull requests | List, open in browser, check out, create from a branch (GitHub via gh, GitLab via glab) | Left sidebar |
| Terminal | Tabbed, real pseudo-terminal, your own shells, colours, scrollback, copy | Bottom panel |
| Undo / redo | Commits, amends, merges, rebases, pulls, resets, cherry-picks, reverts, checkouts, branches, tags, stashes | Ctrl+Z / Ctrl+Y |
| File history & blame | Every commit that changed a file (following renames); blame with newer changes marked brighter | File menu |
Beyond the six: the details that show it is a serious tool
The headline features are real, but the depth is in the smaller ones. Staging works at three levels: whole files, individual hunks (each hunk of a diff has Stage hunk, Discard hunk and Unstage hunk), and selected lines — click the changed lines you want, Shift+click for a range, and stage, unstage or discard only those. The commit box commits with Ctrl+Enter, stages everything if nothing is staged, and offers Amend last commit with a warning when the commit is already pushed. You can also save multiple commit identities and switch a repository between them.
Comparison is thoughtful too. Ctrl+click a second commit (or Compare with… in the commit menu) to list the files that differ between the two and open each diff, with the Uncommitted changes row standing for the working tree. On a branch, Changes x adds to main shows only what it changed since the two diverged, the way a pull request shows it, while Compare main with x shows every difference; a checkbox switches between the two, and the right pane says how many commits each side has that the other has not.
There is a command palette (Ctrl+P) with every action and branch, fuzzy matched, and a built-in manual (F1) explaining each part and every shortcut. Settings cover zoom, avatars, notifications, background fetch and the default shell; the app checks GitHub every 12 hours for a newer release. Themes are Dark, Medium Gray and Light, taken from PhotoCraft's Pro palettes.
The release history shows how fast it is moving. Version 0.3.0 added partial staging, compare and code search; 0.3.1 added per-tab icons and colours; 0.3.2 added in-place message editing; 0.3.3 added draggable tabs and a settings tab; and v0.3.4, released 15 November 2026, reworked the diff view and added stashes to the graph as dashed boxes above the commit they were made on. Community contributions are already landing — the v0.3.4 diff improvements came from a contributor, JKamsker, credited in the release notes.
Install, step by step
Ready-made builds for Windows, Linux (x86-64) and macOS (Apple silicon and Intel) are on the releases page. Git must be installed first — GitCraft drives it, it does not bundle it.
Windows. Download gitcraft-v0.3.4-windows-x86_64-setup.exe (or the matching version when a newer release lands). The installer works for your user with no administrator rights, adds a Start menu entry, an optional desktop icon, an Open in gitcraft entry on folders, and an uninstaller. The .zip is the same program without installing.
Linux. Three routes, depending on your distribution:
sudo apt install ./gitcraft-v0.3.4-linux-x86_64.deb # Debian, Ubuntu, Mint sudo dnf install ./gitcraft-v0.3.4-linux-x86_64.rpm # Fedora, openSUSE chmod +x gitcraft-v0.3.4-linux-x86_64.AppImage # any distribution ./gitcraft-v0.3.4-linux-x86_64.AppImage
The .deb and .rpm install with an applications menu entry. The AppImage runs anywhere: make it executable and run it, and Add gitcraft to the applications menu on the start page (or in Settings) adds a menu entry that follows the AppImage when you replace it with a newer one. A .tar.gz holds the bare binary and a .desktop file. Note the Linux builds are x86-64 only — there is no ARM build in the releases as of v0.3.4.
macOS (11 or later). Open the universal .dmg and drag gitcraft to Applications; the .zip holds the same app. The app is not notarized by Apple, so macOS refuses to open it the first time. Fix it in System Settings under Privacy & Security by clicking Open Anyway, or from the terminal:
xattr -dr com.apple.quarantine /Applications/gitcraft.app
Git comes with the Xcode command line tools (xcode-select --install) or Homebrew. When GitCraft is opened from the Finder or the Dock, the commands it starts (git, gh, glab, your editor, the terminal) get your login shell's PATH, so Homebrew installs are found.
Build from source. If you have a Rust toolchain, the repository builds the usual way. Linux needs the usual eframe system packages (for example libxkbcommon-dev, libgtk-3-dev for the file dialogs, libdbus-1-dev for notifications). Pull requests need the GitHub CLI (gh) or GitLab CLI (glab), logged in:
cargo run --release # start cargo run --release -- path/to/repo # open a repository directly cargo test
gh or glab first — the pull-request list, checkout and creation all go through those CLIs. Without them, everything else still works; only the pull-request panel stays empty.GitCraft vs the other Git GUIs
| Client | Price | Tech | Platforms | Standout strength | The catch |
|---|---|---|---|---|---|
| GitCraft | Free, open source (Apache-2.0) | Rust + egui, native | Windows, Linux, macOS | Light and fast; undo for almost every action; drives system Git | Three weeks old; tiny community; no Linux ARM build; macOS not notarized |
| GitKraken | Paid plans (free tier limited) | Electron | Windows, Linux, macOS | Polished graph, built-in merge tool, deep hosting integrations | Heavier Electron app; the good parts sit behind a subscription |
| Sourcetree | Free | Native (Atlassian) | Windows, macOS only | Free, mature, strong staging and submodule support | No Linux version; development pace is slow |
| GitHub Desktop | Free, open source | Electron | Windows, macOS (Linux via community builds) | The simplest Git GUI to learn; excellent GitHub flow | GitHub-centric; deliberately hides advanced Git (no interactive rebase UI) |
| lazygit | Free, open source | Terminal UI (Go) | Windows, Linux, macOS | Keyboard-driven, fast, runs anywhere a terminal runs | It is a text interface, not a graphical one — no mouse-driven diffs or graph |
The honest read: GitCraft's natural rivals are GitKraken and Sourcetree, the graph-based GUIs, and its pitch against them is weight — a native Rust binary instead of Electron, and a price of zero with the source open. Against GitHub Desktop it wins on depth (interactive rebase, worktrees, blame, partial staging) and loses on simplicity and polish. Against lazygit it is a different kind of tool entirely: lazygit is faster for keyboard users who live in a terminal, while GitCraft is for people who want to see the graph and click through diffs.
One more comparison matters: the command line itself. GitCraft does not replace it — it wraps it, and the built-in terminal sits one click away. If you already live in the terminal, GitCraft adds a graph, a diff view and undo. If you have never liked the terminal, GitCraft still expects Git to be installed. It is a GUI for people who know Git, not a way to avoid learning it.
Honest limitations and fine print
- It is very young. Created 27 October 2026, with 69 stars, 6 forks and 23 commits as of 18 November 2026. Nine releases in three weeks shows momentum, but there is no track record of how it holds up across large repositories, long histories or many teams.
- Small community, small safety net. A handful of contributors so far (the v0.3.4 diff work came from one, JKamsker). If you hit a bug, the fix depends on a small project, not a company.
- macOS is not notarized. The first launch is blocked until you click Open Anyway or strip the quarantine attribute — normal for small open-source Mac apps, but real friction.
- No Linux ARM builds. The Linux releases are x86-64 only. If you run GitCraft on an ARM Linux machine, you will be building from source.
- Git is a hard requirement. There is no bundled Git. If Git is missing, misconfigured or an old version, GitCraft inherits the problem. The same applies to
ghandglabfor pull requests. - Avatars and update checks phone home. Author avatars are fetched from GitHub, GitLab or Gravatar and cached on disk, and the app checks GitHub for new releases every 12 hours. Both can be turned off in Settings, but the defaults send your repository authors' email hashes and your version-check requests out. If that bothers you, switch both off before opening a private repository.
- The "light" claim is relative. Native Rust is lighter than Electron, and that is a real difference. It is not a promise about memory use on a repository with a million commits — history loads 1,500 commits at a time for a reason, and nobody has published benchmarks yet.
Security and privacy
GitCraft is a local desktop app: your repositories stay on your machine, and there is no account, no cloud sync and no analytics in the README. What leaves your machine is decided by the tools it shells out to, not by GitCraft itself — Git talks to your remotes exactly as it would from your terminal, with your own credentials and credential helper. When a remote wants a username and password (or token) and no credential helper provides them, a dialog asks and the operation runs again; the credentials stay in memory for the tab, and Git's own credential helper stores them if there is one.
Two things do reach the network on GitCraft's own initiative: avatar lookups (GitHub's API or gh, GitLab's avatar API, or Gravatar from a hash of the author's email) and the release check against GitHub every 12 hours. Both are switchable off in Settings, and the avatar cache sits on disk. Nothing in the README suggests telemetry, crash reporting or any other reporting.
Before running anything from a three-week-old repository, read the code or at least the release notes — the project is small enough to skim, and the Layout section of the README maps every source file to its job. Download installers and packages only from the releases page, never from a mirror. And the usual rule applies: a Git client can rewrite history, reset branches hard and discard changes, so keep backups of work you cannot afford to lose — GitCraft's undo covers its own actions, not a disk failure.
Frequently Asked Questions
Is GitCraft free?
Yes. It is open source under the Apache License 2.0, and the ready-made builds on the releases page cost nothing. There is a donation badge in the README, but no paid tier and no locked feature.
Is GitCraft new?
Yes — genuinely new. The repository was created on 27 October 2026, and the latest release, v0.3.4, came out on 15 November 2026. It had 69 stars and 6 forks as of 18 November 2026.
Does it work on Linux?
Yes, on x86-64, via a .deb, .rpm, AppImage or .tar.gz. There is no ARM Linux build in the releases as of v0.3.4 — ARM users need to build from source. Linux also needs the usual eframe system packages for file dialogs and notifications.
Does GitCraft replace Git?
No. It drives the Git command line installed on your machine, so your config, credentials, hooks and aliases apply as usual. If Git is not installed, GitCraft's start page will tell you. Think of it as a graphical front end for Git, not a Git of its own.
Can it do interactive rebase?
Yes. Right-click a commit and choose interactive rebase onto it, then pick, reword, squash, fix up or drop each commit and reorder them before starting. Ctrl+Z undoes the whole rebase, and a rebase stopped on conflicts shows an Abort banner with Continue in the commit box.
How is it different from GitKraken or GitHub Desktop?
It is a native Rust app instead of an Electron one, so it starts lighter and stays lighter; it is free and open source with no subscription tier; and it has undo for almost every action. GitHub Desktop is simpler and more polished for beginners, and GitKraken has deeper hosting integrations behind its paid plans — neither has GitCraft's youth risk.
Sources
- GitCraft on GitHub — github.com/Vancete/gitcraft (README, features, download and build instructions; Apache-2.0; created 27 October 2026; 69 stars, 6 forks as of 18 November 2026)
- GitCraft releases — github.com/Vancete/gitcraft/releases (v0.3.4 latest, with v0.3.0–v0.3.3 notes)
- v0.3.4 release — 15 November 2026 (diff rework, stashes in the graph, draggable tabs)
- Asad Webs free tools — no Git-related tool exists in the collection as of 18 November 2026, so this post links the tools index rather than a fitting tool.
Related on Asad Webs: if you work with developer tooling, see uv: The Python Package Manager, Herdr: Run AI Coding Agents in Tmux, Arcane: The Docker Manager Developers Are Switching To, Caddy: Free HTTPS, Automatically and Claude-BugHunter: the AI security skills bundle — all verified live on 18 November 2026. For the full collection, browse asadwebs.com/tools.




Be the first to share a useful question or thought.