Repository navigation
Auto-dispatch threads from Planboard state (issue enters plan:todo) #165
Description
What competitors do
OpenAI Symphony polls the tracker and dispatches an agent per issue when it enters an active state (SPEC); ComposioHQ AO does the same via its orchestrator agent.
Solenta today
The Planboard requires a manual click per issue (Start task in src/components/PlanboardView.tsx:236). electron/automations.js:151-193 is a purely time-based scheduler; nothing watches issue labels or state transitions. Solenta already has the kanban, the plan:* labels (electron/issues.js:285), and thread creation from issues.
Why it matters
Auto-dispatch on "moved to plan:todo" turns the Planboard from a launcher into an actual pipeline. Combined with the concurrency cap and the CI reaction loop, this is the coherent "autonomous planboard" arc.
Scope suggestion
Opt-in per project: poll open plan:todo issues on an interval, start a thread per new one (respecting the global concurrency cap), move the label to plan:doing, and stop on plan:done/closed.
Activity
currentbits commentedon Aug 17, 2026
Research note (Modal named sandboxes): use a name-based singleton constraint (e.g. name = issue#123) in the dispatch queue so duplicate dispatches for the same issue fail fast instead of forking two workers for one task.
Merge pull request #334 from currentbits/coder/auto-dispatch-threads-…
currentbits commentedon Aug 17, 2026
Research note (linear-agents, Symphony fork): put the autonomy gate ON the issue — an 'Agent Autonomy: AFK/HITL' label decides per-task whether dispatch is automatic or human-gated. Also: stacked PRs for dependency-ordered issues (downstream PRs open while blockers pend, ties to #251).