Built with Rust
AI-Native

From ticket to PR
in one command.

Run 5 AI agents in parallel — zero index.lock conflicts. git-parsec gives every agent its own isolated worktree, tied to your issue tracker. No retries, no wasted tokens, no merge chaos.

Get Started View on GitHub GitHub Stars
parsec -- zsh
# Run 5 AI agents in parallel — no lock conflicts $ parsec start CL-2283 ✓ Created worktree for CL-2283 Title: Collect HeuristicCompletionException handling Branch: feature/CL-2283 Path: ../myproject.CL-2283   # Each agent gets its own isolated worktree $ parsec start CL-2290 ✓ Created worktree for CL-2290   # Ship it -- push, create PR, cleanup $ parsec ship CL-2283 ✓ Pushed feature/CL-2283 ✓ PR created: github.com/org/repo/pull/42 ✓ Worktree cleaned up  
The Problem
Git wasn't built for
AI agent workflows.

When AI agents run in parallel on the same repo, they collide on .git/index.lock — crashing mid-task, burning tokens on retries, and leaving broken state. Worktrees solve isolation, but lack the lifecycle management agents need.

Without parsec

  • Lock contention

    Parallel git operations collide on .git/index.lock, blocking agents and developers.

  • Manual worktree management

    Create branch, add worktree, remember paths, clean up manually. Error-prone and tedious.

  • No ticket connection

    Branches and worktrees have no link to your issue tracker. Context gets lost.

  • Invisible conflicts

    Parallel work silently edits the same files. You only find out at merge time.

With parsec

  • Zero-conflict parallelism

    Each ticket gets its own isolated worktree. No lock contention, ever.

  • One-command lifecycle

    parsec start creates everything. parsec ship pushes, PRs, and cleans up.

  • Ticket tracker integration

    Jira and GitHub Issues built in. Branches auto-named, PR titles auto-filled.

  • Early conflict detection

    parsec conflicts warns when worktrees touch the same files -- before you merge.

  • Full operation history

    parsec log shows everything parsec has done. parsec undo rolls back the last step if something goes wrong.

See it in action
From ticket to PR in 60 seconds.
git-parsec demo showing start, list, switch, log, undo, and clean commands
Features
Everything you need.
Nothing you don't.

A focused toolset for the complete worktree lifecycle -- from creating isolated workspaces to shipping production-ready PRs.

Ticket-driven worktrees

parsec start PROJ-123 creates an isolated worktree, fetches the title from your tracker (Jira · GitHub Issues · GitLab Issues · Bitbucket), and names the branch consistently. parsec adopt and --branch bring existing branches under management. Sibling layout (../repo.ticket/) keeps directories clean and IDE-friendly.

$ parsec start PROJ-123   # worktree + tracker fetch + branch in one call

Stacked PRs done right

Chain workspaces with parsec start CHILD --on PARENT. parsec stack --submit opens every PR in the stack in topological order. Auto-posted "← prev / next →" navigation comments let reviewers walk the chain without leaving the PR view. --sync rebases the whole chain when the base moves.

$ parsec stack --submit   # root first, with nav comments

Multi-forge, multi-CI

Full PR lifecycle on GitHub, GitLab, and Bitbucket Cloud. CI status from Actions, GitLab CI, and Bitbucket Pipelines — all surfaced through the same parsec ci and parsec pr-status commands. Auto-detected from the remote URL.

$ parsec ci --watch   # works the same on any forge

One-step ship + lifecycle

parsec ship pushes, opens the PR, and removes the worktree. parsec merge waits for CI, merges, and cleans up. parsec clean sweeps already-merged branches. parsec conflicts flags cross-worktree file overlap before push. parsec undo reverses the last operation. Every mutating command supports --dry-run.

$ parsec ship PROJ-1234   # push + PR + cleanup, one command

Built for agents

--json on every command. Structured error codes (E001–E013) for programmatic handling. parsec log --export emits JSONL with execution IDs and per-step timing. --offline and headless modes for CI / air-gapped environments. The config JSON Schema is published to schemastore.org for editor autocomplete.

$ parsec log --export | jq 'select(.duration_ms > 1000)'

Build cache + ergonomics

[worktree].shared_cache shares target/, node_modules/, .venv/ from the main repo to new worktrees via symlink (default) or copy — eliminates cold-build cost on parsec start. Shell integration auto-cd's, tab completions ship for zsh / bash / fish / powershell, parsec doctor validates your setup.

shared_cache = ["target", "node_modules", ".venv"]
More features — 16 additional capabilities
Branch sync — parsec sync rebases or merges the latest base branch into one or all worktrees.
Operation history — parsec log shows every action with timestamps; filter by ticket or last N.
Undo — parsec undo reverses the last start / ship / clean. Use --dry-run to preview.
Open in browser — parsec open launches the PR or ticket page (GitHub / GitLab / Jira / Bitbucket).
Worktree diff — parsec diff compares any worktree to its base branch (--stat, --name-only).
Compress branch — parsec compress squashes commits into one tidy commit before shipping.
PR template auto-fill — ship --template reads .github/PULL_REQUEST_TEMPLATE.md.
Reviewers + labels — ship --reviewer / --label at PR creation time, or set defaults in config.
Draft-by-default — [ship].draft = true opens every PR as a draft for WIP review.
Pre-ship hooks — run cargo test, npm run lint, etc. before ship via [hooks].pre_ship.
Sprint board — parsec board renders the active Jira sprint as a Kanban board in the terminal.
Issue creation — parsec create / new-issue opens tickets in your tracker; --start immediately creates a worktree.
Release workflow — parsec release merges develop → main, tags, and creates a GitHub Release.
Policy guard — [policy] blocks ships to protected branches and restricts allowed targets.
Headless mode — --yes and TTY auto-detection skip prompts in CI / agent environments.
Cross-platform — Linux / macOS / Windows. Windows UNC path handling via the dunce crate.
See the full command reference for every flag and example, or read the getting started guide.
Comparison
How parsec stacks up.

parsec fills the gap between bare git worktree commands and tools that don't connect to your issue tracker.

Feature parsec worktrunk git worktree git-town GitButler
Ticket tracker integration Jira + GitHub Issues -- -- -- --
Physical isolation (worktrees) Yes Yes Yes -- Virtual branches
Cross-worktree conflict detection Yes -- -- -- --
One-step ship (push + PR/MR + clean) GitHub + GitLab -- -- Yes --
Operation history & undo Yes -- -- Yes (undo) Yes
JSON output for AI agents Yes -- -- -- Yes
CI monitoring Yes (--watch) -- -- -- --
Stacked PRs Yes -- -- Yes Yes
Post-create hooks Yes Yes -- -- --
Auto-cleanup merged worktrees Yes -- Manual -- --
Forge support GitHub + GitLab GitHub -- GH, GL, Gitea, BB GitHub + GitLab
Zero config start Yes Yes -- -- --
Quick Start
Up and running in 60 seconds.

Three commands from install to your first PR.

01

Install

Install via cargo. A single binary, no runtime dependencies.

cargo install git-parsec
02

Configure

Run interactive setup. Enable shell integration for auto-cd and merge recovery.

parsec config init
eval "$(parsec init zsh)"
03

Start building

Create a worktree from any ticket. Code, commit, and ship when ready.

parsec start PROJ-42
full workflow demo
# Create isolated workspace from Jira ticket $ parsec start CL-2283 ✓ Created worktree for CL-2283 Branch: feature/CL-2283 Path: ../myproject.CL-2283   # Switch into the worktree $ parsec switch CL-2283 cd ../myproject.CL-2283   # ... do your work, commit as usual ...   # Check for conflicts with other worktrees $ parsec conflicts ✓ No file conflicts across 3 active worktrees   # Ship it -- push, create PR, cleanup $ parsec ship CL-2283 ✓ Pushed feature/CL-2283 (4 commits) ✓ PR #42 created: github.com/org/repo/pull/42 ✓ Worktree cleaned up
Installation
Install parsec.

A single Rust binary. No runtime dependencies, no node_modules, no Python virtualenvs.

Cargo cargo install git-parsec Available
Homebrew brew install git-parsec Coming soon
From source git clone && cargo build --release Available
Let your AI agents run.
Zero conflicts. Zero wasted tokens.

Join developers and AI teams who use parsec to run parallel agents on the same repo — isolated worktrees, no index.lock fights, fewer retries.

Star on GitHub
$ cargo install git-parsec