A bounded orchestrator
The orchestrator plans, delegates, reviews, and synthesizes. Workers remain responsible for repository changes.
All product areas
05 / Agent Swarms
A fixed roster coordinated around one outcome.
Build a reusable team with a read-only orchestrator and named workers. Each member can use a different CLI, model, effort level, and role while the entire run remains observable.
Actual Agent Swarms capture
WHAT IT CHANGES
Less reconstruction.
More visible progress.
Parallel when it is safe
Independent assignments can run together; dependent work waits for the integrated state it needs.
A topology you can touch
Move the graph, open any agent terminal, message a team member, and spot blocked work immediately.
A reusable fixed roster
Give named workers roles, instructions, CLI, model, and effort settings once, then bring the same team to the next goal.
Plans remain yours to approve
Edit the orchestration brief, request a revision, or inspect advanced assignments and dependencies before dispatch.
GitHub work stays connected
Mirror a Project board, start labelled Ready issues, create linked worker issues, and return verified work as a connected pull request.
WHAT IS BUILT IN
The working surfaces behind Agent Swarms.
Configure people, roles, and policy
Choose from role presets or write custom instructions, restrict members to available CLIs, set concurrency and revision limits, and opt into automatic dispatch only when wanted.
Approve the work before workers start
Read the orchestrator’s final message, submit a plain-language revision, or open advanced controls for ownership, dependencies, file hints, and completion criteria.
Watch the team as a system
Pan, zoom, resize, and save the topology. Status colors expose active, waiting, approval, blocked, and completed agents while terminals remain one click away.
Tie a run to the original request
Switch between the visualizer and a GitHub-synchronized board, move cards deliberately, and keep sub-issues, status, review, PR, and merge completion aligned.
HOW IT WORKS
A deliberate path through Agent Swarms.
- 01
Create the roster
Name workers, choose their roles, and configure the available CLI, model, and effort for each one.
- 02
Approve the plan
Review the orchestrator’s final planning message, request a revision, or edit the advanced work items.
- 03
Follow dispatch and integration
Message any member now or queue context for their next idle point while isolated worker branches progress.
- 04
Review the team result
Follow retries, verification, integration, browser review, local apply, and the linked pull request from one run view.
KEEP EXPLORING