diff --git a/.story_kit/bugs/bug-2-agent-panel-expand-does-nothing.md b/.story_kit/bugs/archive/bug-2-agent-panel-expand-does-nothing.md
similarity index 100%
rename from .story_kit/bugs/bug-2-agent-panel-expand-does-nothing.md
rename to .story_kit/bugs/archive/bug-2-agent-panel-expand-does-nothing.md
diff --git a/.story_kit/bugs/bug-3-stale-worktree-blocks-agent-start.md b/.story_kit/bugs/archive/bug-3-stale-worktree-blocks-agent-start.md
similarity index 100%
rename from .story_kit/bugs/bug-3-stale-worktree-blocks-agent-start.md
rename to .story_kit/bugs/archive/bug-3-stale-worktree-blocks-agent-start.md
diff --git a/.story_kit/bugs/bug-4-run-button-does-not-start-agent.md b/.story_kit/bugs/bug-4-run-button-does-not-start-agent.md
new file mode 100644
index 0000000..f0c288b
--- /dev/null
+++ b/.story_kit/bugs/bug-4-run-button-does-not-start-agent.md
@@ -0,0 +1,24 @@
+---
+name: Run button does not start agent
+---
+
+# Bug 4: Run Button Does Not Start Agent
+
+## Symptom
+
+Clicking the "Run" button in the AgentPanel does not visibly start an agent. No feedback is shown to the user.
+
+## Root Cause
+
+When multiple agents are configured in `project.toml` (e.g. supervisor, coder-1, coder-2), `handleRunClick` shows a role-selector dropdown instead of starting an agent directly. The dropdown may not be visible due to layout/positioning issues, or the click handler may be swallowed.
+
+## Reproduction Steps
+
+1. Start the server and open the web UI
+2. Expand a story in the Agent panel
+3. Click the "Run" button
+4. Observe: nothing visible happens (no agent starts, no dropdown appears)
+
+## Proposed Fix
+
+Investigate whether the role-selector dropdown is rendering but hidden (z-index, overflow, positioning), or whether the click event is not reaching `handleRunClick`. If the dropdown is the issue, consider starting the default agent directly and offering role selection separately.