No staging area, no stash
There's no git add dance and no stash to lose track of. Every change in your working copy is simply part of the current commit. You move work between commits instead of shuttling it through an index.
Why wyrm
You already know Git.
Here's what jj changes.
Jujutsu (jj) keeps Git's storage and forges — your repos, your remotes, your pull requests all still work — and rethinks the parts of the workflow that fight you daily. wyrm is the GUI built for that workflow from day one, not bolted on after.
The mental-model shift
Nothing here asks you to relearn version control. It's mostly things you already wished Git did — and a few moments where it just stops getting in your way.
The working copy is a commit
jj snapshots your working directory as a real commit automatically. Editing files amends it; describing it gives it a message. The thing you're working on is always a first-class object in the graph, not a pile of uncommitted edits.
Conflicts don't block you
A conflict is a recorded state, not a wall. A rebase or merge always completes — the conflict travels with the commit, and you resolve it whenever you like. wyrm gives that state a real three-way editor with per-hunk decisions.
Undo anything, via the op log
jj records every operation — every commit, rebase, and bookmark move — in an operation log. Made a mess? jj undo walks it back. wyrm surfaces that log so "undo the last thing I did" is a real, visible button, not a prayer to the reflog.
How wyrm compares
Honest version: the Git-GUI field is mature and good at Git. wyrm's edge is that it's jj-native — and indie. Cells we can't speak to fairly are left as "—" or "varies".
| Capability | wyrm | GitKraken | plain jj CLI | other git GUIs |
|---|---|---|---|---|
| jj-native (built for jujutsu) | Yes — primary VCS | No | Yes (it's jj) | Rarely |
| Visual log graph | Yes — virtualised, 30k commits | Yes | ASCII in terminal | Usually |
| First-class conflict resolution | Yes — 3-way, per-hunk, reversible | Merge tool | In-tree, edit by hand | Usually |
| Operation-log undo | Yes — visible op log | — | jj undo | — |
| Workspaces (multiple working copies) | Yes — in the UI | Git worktrees, varies | jj workspace | Varies |
| Push / PR preview before you push | Yes — full diff + force-push warning | Varies | Manual diff | Varies |
| Price model | Free for one repo · annual Pro/Business | Paid subscription | Free & open source | Varies |
| Platforms | Native macOS today | Cross-platform | Cross-platform | Varies |
| Telemetry | No in-app tracking | Varies | None | Varies |
| Indie / independent | One dev, no VC | Company-backed | Open-source project | Varies |
Competitor columns are kept general on purpose — features and prices move, and we'd rather be vague than wrong. Check each tool's own site for specifics. "Native macOS today" reflects wyrm's current release; more platforms are on the roadmap.
Free for one repo, forever
The whole local experience — the log graph, conflict resolution, the operation log, diffs — is free on one repository, for as long as you want. No trial clock on the core, no feature held hostage behind a login.
When you outgrow a single repo, Pro unlocks unlimited repositories (with Business for teams). Both are annual-only and priced to be the easy yes — early subscribers lock in launch pricing for the life of the subscription. The full breakdown lives on the pricing page.
No VC money, no enterprise upsell theatre, no analytics watching what you click in the app. wyrm is funded by the people who pay for Pro — which is exactly how it stays independent.