agents

/agents — Parallel Agent Orchestrator

You are the orchestrator. You will launch 1-10 parallel Claude Code agents, each working autonomously on a beads task in its own git worktree. Follow these phases exactly.

Arguments: $ARGUMENTS

---

Phase 1 — Parse Arguments & Fetch Tasks

Parse the following flags from $ARGUMENTS (all optional):

Flag	Default	Description
--auto-merge	off	Agents auto-merge PRs after CI passes
--count N	(interactive)	Max number of tasks to select
--model MODEL	sonnet	Model for spawned agents (ignored when --agent is set, since the agent definition specifies its own model)
--budget N	5	Max USD per agent
--agent NAME	(none)	Use an existing agent definition from .claude/agents/NAME.md. Multiple instances of the same agent run concurrently — the file is a reusable template, not a per-instance resource.

Fetch tasks

First, check if bd (beads) is available:

command -v bd

If bd is available, fetch tasks:

bd ready --json

Then continue to Phase 2 with the beads task list.

If bd is NOT available (or returns no tasks), offer a manual task mode. Ask the user to describe the tasks they want agents to work on. Accept a list of task descriptions, one per agent. For example:

No beads tasks found. You can specify tasks manually.

How many agents do you want to launch? Enter task descriptions (one per line, empty line to finish):

  1. Fix the login page redirect bug
  2. Add unit tests for the payment module
  3. Refactor the database connection pool

For manual tasks, generate synthetic task IDs (e.g., TASK-1, TASK-2, etc.) and use the descriptions as both the title and description in later phases.

---

Phase 2 — Select Tasks

If using beads tasks, present them as a numbered list:

Available tasks:
  1. [BD-123] Fix auth token refresh logic
  2. [BD-456] Add pagination to /api/users
  3. [BD-789] Update error messages for form validation
  ...