OpenCode Swarm plugin
OpenCode plugin that turns a session into a team of agents led by an architect and runs the work through plan phases
- 514 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The installer changes OpenCode settings and disables the built-in explore and general agents in opencode.json
- Agents write files and run commands
- Optional features work with git worktrees, the GitHub CLI and GitHub Actions
Install
- Works in
Manual install
bunx opencode-swarm installRequires Bun 1.3.13 or newer. The installer registers the plugin and creates a config at ~/.config/opencode/opencode-swarm.json.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The installer changes OpenCode settings and disables the built-in explore and general agents in opencode.json
- Agents write files and run commands
- Optional features work with git worktrees, the GitHub CLI and GitHub Actions
This is third-party code. Review the repository files before installing.
What it does
OpenCode Swarm turns a single OpenCode session into a team of roles led by an architect. One agent writes code, another reviews it, a third writes and runs tests, and a fourth checks security. A task counts as done only when every required check passes. The `/swarm agents` command shows the current roster. Given a request such as "build me a JWT auth system", the architect asks only what it cannot infer from the code, scans the codebase and consults domain experts when needed. It then writes a phased plan, and a critic reviews it before work starts. Every task goes through a pipeline of code, automated checks, review, tests and a regression sweep. Failures go back to the implementer with structured feedback, and state is saved in the project, so a session can resume another day. Modes switch by command. Balanced is the default, Turbo speeds up iteration, and Lean Turbo runs parallel lanes for tasks that do not overlap. Full-Auto lets safe operations through on its own and routes risky ones to the critic. Epic is opt-in and runs a large plan in waves inside isolated git worktrees.
Who it is for. For OpenCode developers who want writing, review and testing split between roles, with a record of evidence for every phase.
Good fit when
- A large feature should split into phases so a critic reviews the plan before the first line of code
- You want review and tests for every task in the plan
- Work on a feature will stretch over several days with breaks
- Pull requests and CI should be tracked from the session through `/swarm pr subscribe`
- Implementation should start from GitHub: the `swarm-implement.yml` action runs on the `swarm:implement` label on an issue
Not a fit when
- You need a tiny one-file edit: the pipeline of roles and checks is slower than a plain session
- You work outside OpenCode: the plugin exists only for it
- Your model budget is tight: every task passes through several roles and repeated checks
Example request
Build JWT authentication in this project: write a plan, run it past the critic, then implement task by task with review and testsLimitations
- Installing needs Bun 1.3.13 or newer, or Node.js 22.13 or newer when you install through npm.
- The plugin works only when the Swarm architect is selected in OpenCode. Under another agent the gates, reviewers and testers do not run.
- In Full-Auto mode the agent decides on its own which operations are safe, so turn it on deliberately.
- Epic stays a preview feature and is enabled with `epic.mode.enabled: true`. Automatic GitLab polling is still planned.
- External skill curation, the skill optimizer and PR monitoring are off by default.
How to disable. In the OpenCode agent picker choose any agent other than the Swarm architect. To remove the plugin entirely, delete opencode-swarm from the plugin list in opencode.json and re-enable the agents the installer turned off. Delete ~/.config/opencode/opencode-swarm.json and the project's .swarm/ folder by hand.
FAQ
How do I install OpenCode Swarm?
Run `bunx opencode-swarm install`. The command installs the package, registers the plugin in OpenCode and creates the ~/.config/opencode/opencode-swarm.json config.
Why is Swarm not reviewing my code?
Most likely another agent is selected in OpenCode. You pick the Swarm architect in the agent or mode picker.
What does the installer change in OpenCode settings?
It registers the plugin, writes the global config, creates a project config when missing and disables the built-in explore and general agents in opencode.json.
How is Balanced different from Turbo?
Balanced is the default and pairs high safety with medium speed. Turbo is faster: at phase completion it skips gates 1–5 and keeps stages A and B for every task.
Where is progress stored?
In the project's .swarm/ folder: plans, evidence, context, knowledge and telemetry. If the folder exists, the architect goes straight to resume and execute.
Discussion
No questions or reviews yet.
Related
PluginsA Claude Code plugin with seven specialized subagents and approval gates: the agent proposes a plan and waits for confirmation before touching code
55 skills for Claude Code, Codex, OpenCode and Pi: code review, security audit, feature development, frontend design and Hugging Face
A Telegram bot for OpenCode: send coding tasks, watch progress and switch models from your phone while OpenCode keeps running on your own computer
A Claude Code and Codex plugin with skills for code research, tests, refactoring and independent review of finished changes
A Grid Dynamics plugin that loads a team's shared engineering standards, architecture and workflows into a coding agent session
A plugin for Codex and Claude Code that runs a task through a chain of roles from planning to an independent audit
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Repository stars | Main difference |
|---|---|---|---|
| OpenCode Swarm (this entry) | no | 514 | |
| oh-my-openagent | no | 70,474 | an orchestrator for OpenCode and Codex CLI with hooks and an ultrawork mode, while Swarm builds a review and test pipeline with mandatory gates |
| oh-my-opencode-slim | no | 9,844 | an orchestrator hands work to six specialists with different models, while in Swarm an architect leads and a critic, reviewer and tester verify |
README in short
The page starts with the install command, then explains why roles are separated and lists features in a table and a list. Separate sections cover detection of shell file writes, a step-by-step walkthrough and execution modes. Details live in the repository documentation.