Parallel AI agent isolation for Git repositories.

git-lanes enables multiple AI coding agents (Claude Code, Cursor, Aider) to work simultaneously on the same Git repository without creating conflicts. Each agent gets its own isolated lane — a dedicated branch and worktree — so they never step on each other's work.

• Problem
• Features
• Installation
• Quick Start
• Commands
• Configuration
• Adapter Support
• Architecture
• Requirements
• Contributing
• License

When multiple AI agents edit code simultaneously in a repository, they:

• Overwrite each other's changes
• Create merge conflicts
• Produce messy, interleaved commit histories
• Lose work during crashes or timeouts

git-lanes solves this by giving each agent its own isolated workspace with automatic change tracking, conflict detection, and clean PR generation.

• 🔀 Session Isolation — Each agent gets a dedicated Git worktree and branch, mapped by process ID
• 📝 Change Tracking — Automatic tracking of file modifications with commit history
• ⚠️ Conflict Detection — Built-in detection of file overlaps across active sessions with resolution suggestions
• 💾 Work Preservation — Auto-checkpoint captures work during timeouts or crashes via WIP commits
• 🧹 Clean PR Generation — Squash incremental edits into reviewable commits and generate pull requests
• 🔌 Multi-Adapter Support — Hooks for Claude Code, Cursor, and Aider
• 🌐 Multi-Forge PRs — Create pull requests on GitHub, GitLab, or Bitbucket
• 🔒 File Locking — Prevent race conditions with atomic manifest operations
• 📦 Zero Dependencies — Uses only Bun built-ins, no external runtime packages

# Install globally
bun install -g git-lanes

# Or use npx
bunx git-lanes <command>

# 1. Start a session
git lanes start add-search-feature

# 2. Work normally — files are tracked automatically
# (your AI agent edits files here)

# 3. Commit your changes
git lanes commit -m "add search component with fuzzy matching"

# 4. Check for conflicts with other sessions
git lanes conflicts

# 5. Run tests
git lanes test

# 6. Create a pull request
git lanes pr --title "Add search feature with fuzzy matching"

# 7. End the session
git lanes end

Create a .lanes.json file in your repository root:

{
  "shared_dirs": ["node_modules", ".venv"],
  "main_branch_policy": "block",
  "force_cleanup": "prompt",
  "adopt_changes": "always",
  "branch_prefix": "lanes/"
}

git lanes install-hooks --adapter claude-code

Installs three hooks that fully automate the git-lanes workflow:

Once installed, Claude Code will automatically track every file it touches. You just need to start a session:

git lanes start my-feature
# Claude Code works — files are auto-tracked
# When Claude exits, uncommitted changes are saved as WIP
git lanes merge

git lanes install-hooks --adapter cursor

Installs pre-save hooks for automatic file tracking.

git lanes install-hooks --adapter aider

Installs pre-edit hooks to ensure session isolation.

git-lanes uses Git's native worktree feature to create isolated workspaces:

your-repo/
  .lanes/
    worktrees/
      feature-a/    # Agent 1's isolated workspace
      feature-b/    # Agent 2's isolated workspace
  .git/
    lanes-manifests/
      feature-a.json  # Session metadata
      feature-b.json

Each session consists of:

• A Git branch (e.g., lanes/feature-a)
• A Git worktree (isolated working directory)
• A manifest (JSON metadata tracking changesets and pending files)

See ARCHITECTURE.md for detailed technical documentation.

• Bun 1.0+ (or Node.js 20+ for npm installation)
• Git 2.20+ (for worktree support)
• GitHub CLI (gh) — optional, for git lanes pr with GitHub
• GitLab CLI (glab) — optional, for git lanes pr --forge gitlab

See CONTRIBUTING.md for development setup and guidelines.

MIT