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

Archive bugs 2-3, file bug 4: Run button does not start agent

Browse Source 
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Dave
2026-02-20 13:17:48 +00:00
parent 1eae2410f3
commit ce37a70f9a
3 changed files with 24 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

0
.story_kit/bugs/bug-2-agent-panel-expand-does-nothing.md → .story_kit/bugs/archive/bug-2-agent-panel-expand-does-nothing.md
View File

0
.story_kit/bugs/bug-3-stale-worktree-blocks-agent-start.md → .story_kit/bugs/archive/bug-3-stale-worktree-blocks-agent-start.md
View File

24
.story_kit/bugs/bug-4-run-button-does-not-start-agent.md Normal file
View File

@@ -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.