Rebase Canvas
A desktop GUI that wraps the new `git history` command with a visual branch graph, a before/after preview of every commit and ref that will be rewritten, and a one-click confirm — so teams can adopt fixup/reword/split without ever running a blind rebase.
Software engineers and tech leads working on long-lived feature branches who want jj-style safety inside their existing git workflow
- Side-by-side branch graph showing the current tree and the projected tree after a fixup, reword, or split, with affected refs highlighted
- Conflict pre-check that refuses to run the operation if the resulting history would diverge from any other local branch the way raw git would silently break
- Atomic undo: every run is wrapped in `git update-ref` snapshots so a bad outcome can be reverted in one command
- Team presets (per-repo) that lock in conventions like 'split commits larger than N lines' or 'reword before fixup' for consistent PRs
The `git history` subcommands shipped in core git 2.54 (April) and 2.55 (June 2026), got burst-of-attention launches and then dropped off the discussion radar — there's a window right now to become the de-facto visual front-end before the community settles on a CLI-only habit.
Visual rebase/branch-graph tools are clearly in demand — Fork, GitKraken, Tower, Sublime Merge, Lazygit, and VisualJJ all market this exact capability and review sites rank them by it.Best Git GUI Clients 2026: 7 Desktop Apps Ranked for Speed & Usability ↗Best Git Clients in 2026: GitKraken vs Fork vs Lazygit ↗
Saturated incumbents already cover visual interactive rebase (Fork, GitKraken, Tower, Sublime Merge, Lazygit), and VisualJJ is a near-identical direct competitor ('visual interface for Jujutsu, running on the Git repo you already have'); I could not verify the claimed `git history` core subcommand in git 2.54/2.55 — no search result confirms it exists.VisualJJ – Jujutsu with your Git ↗Best Git GUI Clients in 2025: GitKraken, SourceTree, Fork, and More Compared ↗
Willingness to pay exists (GitKraken subscription, Fork one-time, Tower paid) but the wrapper-only value-add is thin against incumbents and VisualJJ has struggled to monetize despite focus — a generic rebase GUI is commodity.Best Git Clients in 2026: GitKraken vs Fork vs Lazygit ↗
Built on the assumption that a `git history` subcommand is now standard CLI surface — unverified, and if it is real, GUI front-ends become commoditized fast and jj itself (with first-class visual tools) is the bigger long-term threat to plain git rebase workflows.
A Tauri/Electron desktop app that shells out to `git`/`jj`, renders a graph, and diffs commits is well-trodden engineering territory; the only risk is the underlying `git history` subcommand appearing to not exist publicly.