Git built for
parallel work.
SproutGit makes worktrees the default — so humans and AI agents can build in parallel without context collisions.
SproutGit makes worktrees the default — so humans and AI agents can build in parallel without context collisions.
The problem with branch-first tools
Traditional Git clients treat branches as the unit of work. But branches are just pointers — they all share the same directory. So context-switching means stashing, checking out, losing state.
This is native Git. git worktree
has been in Git since 2.5 (2015). SproutGit makes it the default workflow with
a clean directory layout, visual management, and lifecycle hooks — no terminal required.
What's in the box
No AI gimmicks, no subscription. Just a fast, honest Git client that treats worktrees as a first-class concept.
Create, switch, and manage Git worktrees in a clean prescribed directory layout. Managed vs external worktrees are visually distinct. The primary checkout is protected.
Lane-based SVG commit graph with search, selection, ref badges, and context menus. Worktree branches are highlighted with distinct markers.
Single-commit and multi-commit range diffs with file list and syntax-highlighted unified diff. Built with Monaco and highlight.js.
Checkout, reset (soft, mixed, hard), and create branches from any ref. Default action creates a branch and a managed worktree together.
Run scripts before and after worktree create, remove, and switch operations. Hooks support dependency ordering and critical/non-critical policy — every hook runs in an interactive terminal tab.
Open any worktree in your configured editor. Respects GIT_EDITOR, core.editor, VISUAL, and EDITOR in that order — your preference, not ours.
Follows system preference. Light and dark themes with the same brand palette and full contrast compliance. No toggle required.
Built with Tauri v2 — a Rust backend and native webview. Small bundle, fast startup, low memory. No Electron, no extra runtime.
Open source · Early preview
SproutGit is an early prototype under active development. The best way to support it is to star the repo, open issues, and contribute.