dave/storkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 7 Wiki Activity

Move story 32 to current and rename to multi-instance worktree support

Browse Source 
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Dave
2026-02-19 16:58:33 +00:00
parent 79d6868a82
commit 12542f10a8
1 changed files with 8 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
.story_kit/stories/upcoming/32_worktree_agent_orchestration.md → .story_kit/stories/current/32_multi_instance_worktree_support.md
View File

@@ -1,23 +1,22 @@
--- ---
name: Worktree Agent Orchestration — Dynamic Port Management name: "Multi-Instance Worktree Support"
test_plan: pending test_plan: approved
--- ---
# Story 32: Multi-Instance Worktree Support
# Story 32: Worktree Agent Orchestration — Dynamic Port Management
## User Story ## User Story
**As a** developer running multiple agents in parallel worktrees, **As a** developer working across multiple git worktrees,
**I want** each server instance to bind to a unique port automatically, **I want** to run separate app instances (server + frontend) per worktree on different ports,
**So that** I can run multiple worktree-based agents concurrently without port conflicts. **So that** I can QA each worktree independently without port conflicts.
## Acceptance Criteria ## 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 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. - [ ] 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). - [ ] 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. - [ ] WebSocket client in the frontend reads the port dynamically rather than hardcoding it.
- [ ] Agent pool can target agents at different worktree server instances by URL.
- [ ] A simple registry or file-based mechanism lets a supervisor discover which ports map to which worktrees. - [ ] A simple registry or file-based mechanism lets a supervisor discover which ports map to which worktrees.
## Out of Scope ## Out of Scope
- Agent orchestration across worktrees (separate story).
- Service mesh or container orchestration. - Service mesh or container orchestration.
- Multi-machine distributed agents (local only for now). - Multi-machine distributed instances (local only for now).