Fix: auto-start agent after spec creation from empty Kanban

[nogataka]

Summary

Fixes #144

When creating a spec from an empty Kanban board (via "Create Spec" button), the agent was not automatically starting after clicking "Continue to Project". Users had to manually click the Play button to start the agent.

Root Cause

SpecCreationChat component is used in two places with different onComplete handlers:

Location	Usage	onComplete behavior
NewProjectModal.tsx	New project creation	✅ Calls startAgent()
App.tsx	Create spec from empty Kanban	❌ Did NOT call startAgent()

The App.tsx version only closed the chat and refreshed queries but did not start the agent.

Changes

• Add startAgent import to App.tsx
• Update onComplete handler to call startAgent() with yoloMode and maxConcurrency parameters

Summary by CodeRabbit

• New Features
  • Agent now automatically initiates after spec creation, eliminating the need for manual startup and streamlining the workflow.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

The PR fixes a bug where the agent fails to automatically start after creating a spec through the Kanban board. It adds the missing startAgent call to the onComplete handler in App.tsx, matching the behavior already present in NewProjectModal.tsx.

Changes

Cohort / File(s)	Summary
Agent Auto-Start on Spec Creation ui/src/App.tsx	Added startAgent import from './lib/api. Updated onComplete handlers in both SpecCreationChat usages to automatically start the agent with yoloMode and maxConcurrency: 3 after spec creation, wrapped in try/catch error handling. Queries are refreshed and spec chat is hidden after agent starts.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5 minutes

Poem

🐰 A spec is born, the agent springs to start,
No waiting, no clicking—just pure bunny heart!
From chat to action, smooth as morning dew,
The Kanban board now knows what to do! 🏃‍♂️✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The PR title accurately describes the main fix: auto-starting the agent after spec creation from an empty Kanban board, which directly matches the changeset in App.tsx.
Linked Issues check	✅ Passed	The PR fully addresses issue #144 by importing startAgent and updating the onComplete handler in App.tsx to call startAgent with proper parameters (yoloMode and maxConcurrency), error handling, and query invalidation.
Out of Scope Changes check	✅ Passed	All changes in App.tsx are directly scoped to fixing the agent auto-start issue; no unrelated modifications or unnecessary changes are present.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[leonvanzyl]

Thank you!