Multi-Session Launch

Multi-Session Launch

Spin up N parallel Claude Code sessions — each with its own terminal, branch, and GitChain logger.

Process

1. Parse $ARGUMENTS for:
   • Number of sessions (default: 3)
   • Project name
   • Base port (default: 7700)
   • Task distribution (what each session should work on)
2. SSH to REACTOR and launch N containers
3. Return grid of terminal URLs

Task Distribution Example

For "Fix login + fix files + fix chat":

Session 7700: "Fix doLogin() — JS scope issue in frontend"
Session 7701: "Fix /api/vault/items 404 — nginx route mismatch"  
Session 7702: "Fix sendChat() — auth header not attached"

Each gets its own branch (session/s-{id}), works in isolation, pushes to shared repo.

Output Format

# ⛓ GitChain Multi-Session: {project}
**{N} sessions launched in ~10s**

| # | Session | Terminal | Task | Status |
|---|---------|----------|------|--------|
| 1 | s-{id1} | [:7700](http://192.168.145.10:7700) | Fix login | ✅ |
| 2 | s-{id2} | [:7701](http://192.168.145.10:7701) | Fix files | ✅ |
| 3 | s-{id3} | [:7702](http://192.168.145.10:7702) | Fix chat | ✅ |

## Dashboard
http://192.168.145.10:9000

## Shared Git Timeline
All sessions push to the same bare repo. View unified timeline:
`git log --all --oneline --graph`

## When Done
Sessions auto-commit. Merge results:
`git merge session/s-{id1} session/s-{id2} session/s-{id3}`

Rules

• Max 10 sessions (port range 7700-7709)
• Each session gets unique branch
• Distribute tasks logically (don't overlap files)
• Include dependency order if tasks depend on each other
• All push to shared bare repo for unified timeline