Armory
Source
Browse
CLIs & Tools

agentswarmOurs

Use to orchestrate a swarm of sub-agents under a CEO pattern when one agent isn't enough but a full visible grid is overkill: break a mission into roles, dispatch them, and coordinate via signal files.

Score
Unranked
Evidence
No signals yet
Last commit
as last read from GitHub; most reads are from 2 Sep 2026 or later
Listed

Install

No one-command install. Set it up from its source.

What it is

A CLI for CEO-style sub-agent orchestration. It decomposes a mission into worker roles, dispatches them, and coordinates completion through a signal-file protocol (done / needs-qa / migrating). It is the dispatch primitive for fan-out work that coordinates via files rather than a live terminal grid.

When to use it

When a mission has several independent sub-tasks that benefit from parallel workers, and you want programmatic coordination via signals. The trigger is "split this into workers and coordinate them."

How to install / invoke

Install globally and invoke with a mission to decompose into roles. Workers signal completion to a shared signal directory the orchestrator polls.

Notes

Pair with agentgrid when you also want the swarm to be visible. Follow the same-worker rule for follow-ups: route a regression back to the worker that already has context rather than broadcasting to the whole swarm.

Related

CLIs & ToolsStable

agentgrid

Use to run many agents in parallel as a visible grid of terminal panes: create an NxM layout, name and monitor panes, broadcast or target prompts, and save/restore whole company configurations.

9 stars
Harnessclaudecodexopencode
orchestrationgridtmuxparallelism
No one-command install · SourceDetails

Not Indexed

  • ceo-launch
  • research-agent
  • recursive-grid