---
name: "Multi-Instance Worktree Support"
---
# Story 32: Multi-Instance Worktree Support

## User Story
**As a** developer working across multiple git worktrees,
**I want** to run separate app instances (server + frontend) per worktree on different ports,
**So that** I can QA each worktree independently without port conflicts.

## Acceptance Criteria
- [ ] Server discovers an available port instead of hardcoding 3001 (e.g., try 3001, then 3002, etc., or use port 0 and report back).
- [ ] Server prints the actual bound port on startup so callers can discover it.
- [ ] Frontend dev server proxy target is configurable (env var or auto-detected from server).
- [ ] WebSocket client in the frontend reads the port dynamically rather than hardcoding it.
- [ ] A simple registry or file-based mechanism lets a supervisor discover which ports map to which worktrees.

## Out of Scope
- Agent orchestration across worktrees (separate story).
- Service mesh or container orchestration.
- Multi-machine distributed instances (local only for now).
