Skip to content

Fan out over the top of the AI queue: one agent per top entry, count set beside the button (default 3) - #1687

Merged
brillout merged 1 commit into
mainfrom
claude/multi-agent-queue-button-zv5evp
Aug 24, 2026
Merged

Fan out over the top of the AI queue: one agent per top entry, count set beside the button (default 3)#1687
brillout merged 1 commit into
mainfrom
claude/multi-agent-queue-button-zv5evp

Conversation

@brillout

Copy link
Copy Markdown
Contributor

Adds the requested button to spin up X agents working on the top X queue entries — one agent per entry — with X set by the user and defaulting to 3.

What it does

Each project header in the Overview's AI Queue card now carries, beside the open-entries badge:

  • a count box (default 3, clamped to 1…MAX_AUTO_PM_CONCURRENCY, the same bound as the routine panel's concurrent-agents setting), and
  • a fan-out button (fast-forward icon) that starts one unattended agent per top open entry, as many as the count says.

Behavior details:

  • One agent pinned per entry. Each agent gets the existing workOnEntryPrompt(entry) — the raw queue line, not the tidied title — for the same reason the drain sweep pins its batch (Setting to set number of concurrent agents #1204): several agents told to work "the first open entry" would all implement the same one.
  • Runs exactly like the single play button (Routine runs started from the dashboard park forever; the same routine from the sweep completes and hands off #1279): unattended, with the user's agent preferences, so gates auto-answer and the armed handoff fires.
  • Sequential starts, first refusal ends the batch — mirroring the auto-PM sweep's own batch loop; the refusal is shown under the list like a single start's.
  • Honest label. The button's label/tooltip names what a click would actually start: capped at the open entries (min(X, open)), singular wording for one.
  • No navigation, unlike the single play button (Click Run now => shows new session instead of the newly created session #1191): a batch has no single agent to follow; the started agents surface in the Agents card right above.
  • Every start button in the card is disabled while a batch is in flight — including between two of its sequential starts, where the shared busy flag briefly drops.

Spec updates (SDD)

  • AiQueue.SPEC.md: new "Fanning out over the top of the queue" section + TL;DR/user-story entries.
  • AiQueue.test.SPEC.md: coverage lines for the new tests.
  • FEATURES-SPEC.md: feature line under "Starting work" (feature explicitly requested, which I've taken as the human approval the file requires).

Tests

7 new tests in AiQueue.test.tsx (default of 3 skipping done entries, count box driving the batch size, cap at open entries, singular label, stop at first refusal, disabled-while-in-flight incl. mid-batch, no navigation); one existing test updated for the second header button. Dashboard suite: 84 files / 827 tests green; pnpm typecheck clean.

🤖 Generated with Claude Code

https://claude.ai/code/session_014rbYrkf4V76bEszetYStXE


Generated by Claude Code

… agent per top entry, the count set beside it (default 3)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014rbYrkf4V76bEszetYStXE
@brillout
brillout merged commit d4b879a into main Aug 24, 2026
2 checks passed
@brillout
brillout deleted the claude/multi-agent-queue-button-zv5evp branch August 24, 2026 12:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants