ABI Superpower: Agent Orchestration

Exposes local multi-agent orchestration as a superpower. Honest scope: Scheduler-backed local workers over existing AI router/constitution paths. No distributed agents, no embedded browser, no new MCP tools.

Actions

multi

Run fixed Abbey/Aviva/Abi trio via scheduler:

abi agent multi "analyze the architecture"

spawn

Run custom workers parsed from name|instructions|hints (semicolon-separated):

abi agent spawn --workers "reviewer|find bugs|plan;optimizer|improve performance|explore" "refactor module"

Options:

• --background — prints task IDs before runAll() (synchronous completion, NOT a detached daemon)

browser

Emit claim-honest local plan (embedded_browser=false, delegation_hint=external-mcp-playwright):

abi agent browser --url "https://github.com" "navigate to github.com"

Options:

• --execute --confirm — REQUIRES literal --confirm token; local planner only runs dry-run; real navigation = external MCP step

plan

Single-agent dry-run planning via the scheduler (maps to abi agent plan, not a multi-worker dry-run):

abi agent plan "inspect WDBX persistence"

For multi-worker execution use multi or spawn. For claim-honest browser planning without navigation use browser (still runs a local dry-run planner worker after printing the plan).

Architecture

Component	Source	Role
Orchestration	crates/abi-ai/src/orchestration.rs	parseWorkerSpecs, defaultTrioSpecs, runCustomMultiAgentWithScheduler, submitAgentsBackground, planBrowserOrchestration
AI module	crates/abi-ai/src/lib.rs	runMultiAgentWithScheduler (fixed trio entrypoint), runAgent / submitAgentTask, re-exports
Scheduler	../wdbx/crates/abi-core/src/scheduler.rs	Local task coordination, memory tracker integration (unconditional core — not a feature flag)
Router	crates/abi-ai/src/router.rs	Abbey/Aviva/Abi profile selection
Constitution	crates/abi-ai/src/constitution.rs	6-principle response audit

Worker Model

• Fixed trio: Abbey (primary empathetic polymath), Aviva (direct expert), ABI (orchestration/governance) — abi agent multi
• Custom: Up to 32 workers (max_worker_count = 32) — abi agent spawn
• Browser: Local planner worker only; real browser = external MCP integration
• Execution: All workers submit through scheduler; --background prints task IDs then blocks on runAll()

CLI Surface

Command	Description
abi agent multi <input>	Fixed trio orchestration
abi agent spawn [--background] [--workers <spec>] <input>	Custom workers
abi agent browser [--url <url>] [--execute --confirm] <task>	Browser planning
abi agent plan <input>	Single-agent planning

Claim Boundary

Per docs/contracts/external-claims-audit.mdx and docs/spec/multi-persona-technical.mdx:

• ✅ Local scheduler-backed multi-worker orchestration
• ✅ Fixed trio + custom workers (≤32)
• ✅ Browser planning with honest embedded_browser=false
• ❌ NOT distributed agents
• ❌ NOT embedded browser (real nav = external MCP)
• ❌ NOT additional MCP tools (frozen 12-tool surface)
• ❌ NOT an autonomous daemon (--background is a compatibility label for a synchronous, fully drained local batch)

Implementation Notes

• Worker fan-out capped at 32
• Background submission is failure-transactional
• Feature-off stubs preserve type ownership
• CLI runtime smoke covers new surface
• MCP HTTP has transport-level wrong-bearer + oversized-body regression tests