git-paw 0.2.0

Parallel AI Worktrees — orchestrate multiple AI coding CLI sessions across git worktrees
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116

# Quick Start: Per-Branch CLI Mode

This walkthrough shows how to assign different AI CLIs to different branches — useful when you want to compare AI assistants or use specialized tools for specific tasks.

## Scenario

You have three branches and want to use:
- **Claude** for the auth feature (complex logic)
- **Gemini** for the API work (lots of boilerplate)
- **Aider** for the database refactor (incremental edits)

## Step 1: Launch git-paw

```bash
cd ~/projects/my-app
git paw
```

## Step 2: Select per-branch mode

```
? How would you like to assign CLIs to branches?
  Same CLI for all branches
> Different CLI per branch
```

## Step 3: Select branches

```
? Select branches (space to toggle, enter to confirm):
  [ ] main
  [x] feat/auth
  [x] feat/api
  [x] refactor/db
```

## Step 4: Assign a CLI to each branch

git-paw prompts you for each branch individually:

```
? Select CLI for feat/auth:
> claude
  codex
  gemini
  aider
```

```
? Select CLI for feat/api:
  claude
  codex
> gemini
  aider
```

```
? Select CLI for refactor/db:
  claude
  codex
  gemini
> aider
```

## Step 5: Watch it launch

```
Creating worktrees...
  ✓ my-app-feat-auth (feat/auth)
  ✓ my-app-feat-api (feat/api)
  ✓ my-app-refactor-db (refactor/db)

Launching tmux session: paw-my-app
  Pane 1: feat/auth → claude
  Pane 2: feat/api → gemini
  Pane 3: refactor/db → aider

Attaching to session...
```

The tmux session shows each pane with its branch and CLI clearly labeled in the pane border:

```
┌─── feat/auth → claude ────────┬─── feat/api → gemini ─────────┐
│                                │                                │
│  Claude is ready to help...    │  Gemini is ready...            │
│                                │                                │
├─── refactor/db → aider ───────┴────────────────────────────────┤
│                                                                 │
│  Aider v0.x loaded...                                           │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘
```

## Comparing approaches

Per-branch mode is great for:

- **A/B testing AI assistants** — give the same task to Claude and Gemini, compare results
- **Specialization** — use a code-generation-focused tool for boilerplate and a reasoning-focused tool for complex logic
- **Trying new tools** — test a new AI CLI on one branch while using your trusted tool on others

## Recovery

Session state captures the per-branch CLI assignments. If your terminal closes or tmux crashes:

```bash
git paw
```

git-paw detects the saved session, recreates tmux, and relaunches each branch with its assigned CLI — no re-selection needed.

## Next Steps

- [User Guide](user-guide/README.md) — session management, presets, dry-run, and more
- [Configuration](configuration/README.md) — save per-branch presets in config