What it does
git-parsec is a command-line tool that manages Git worktrees for ticket-based work. It gives each ticket its own isolated workspace, so several developers or AI agents can run Git commands in the same repository at the same time without index.lock collisions. parsec start creates a worktree and branch and fetches the ticket title from Jira, GitHub Issues, GitLab Issues or Bitbucket. parsec ship pushes the branch, opens a pull request and cleans up the worktree. Other commands cover merging, sweeping merged branches, watching CI, stacked pull requests, undoing the last operation, and flagging conflicts across worktrees before you push. It is built to be driven by agents too. Every command offers JSON output with structured error codes, and there is a JSONL execution log and an offline mode. An MCP server lets Claude Desktop or Cursor call parsec's worktree, pull request, review, CI and sync tools, with confirmation required for changes. The release notes also list AI-generated pull request descriptions. It supports GitHub, GitLab and Bitbucket Cloud as forges. Version 1.0.0, released in September 2026, is described as the final planned feature release.
Capabilities
- Isolated Git worktree for every ticket
- One-command start and ship, from ticket to pull request
- Stacked pull requests with navigation comments
- Conflict detection across worktrees before you push
- JSON output and an MCP server for AI agents
- Jira, GitHub, GitLab and Bitbucket support
When to use it
- You run several AI coding agents in parallel on one repository
- You juggle many tickets at once and want to avoid stashing and branch switching
- You want to go from ticket to pull request without leaving the terminal
- You work with stacked pull requests across GitHub, GitLab or Bitbucket
Alternatives to explore
- GitButler
- worktrunk
- git-town