OpenSwarm CLI
A CLI that reviews code changes, fixes confirmed findings and repeats review before deterministic repository verification.
- 870 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Fix mode changes code; separate commands can push branches and publish pull requests.
- The model provider receives review material and consumes available funds or quotas.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/openswarmDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Fix mode changes code; separate commands can push branches and publish pull requests.
- The model provider receives review material and consumes available funds or quotas.
This is third-party code. Review the repository files before installing.
What it does
OpenSwarm reviews a committed diff or current working-tree changes. In fix mode it groups confirmed findings and gives isolated workers the changes to make. You can use the CLI locally or through the included GitHub Action. An optional daemon adds task orchestration, Linear integration and notifications. Those components are not required for a normal pre-commit review. Workers store task outcomes as repository-specific knowledge and recall them in later prompts.
Who it is for. For developers who want a repeatable review-and-fix cycle with an outcome CI can evaluate.
Good fit when
- Review the current diff without mutating the project before a commit.
- Fix several findings and review the resulting changes again.
- Produce a SARIF report and machine-readable pull-request result.
- Distinguish a pre-existing test failure from a regression.
Not a fit when
- You need a guarantee of defect-free code from one model verdict.
- Your workflow must treat a review that did not run as a success.
- Project policy forbids sending code to the selected model provider.
Example request
Review the current changes with OpenSwarm in read-only mode and show confirmed findings without fixes.Limitations
Review needs a configured provider: Codex, OpenRouter, a local model server or installed Claude Code. The provider receives review material, so check that project policy allows sharing source code with it. On Linux, repository checks require bubblewrap and stop if it cannot provide isolation; configure this separately in CI. Fix mode changes code and executes repository checks, so start with read-only review.
How to disable. Stop the local CLI process. If you enabled the daemon or GitHub Action, disable them separately and revoke provider credentials that are no longer needed.
FAQ
What does exit code 2 mean?
The review did not run, for example because a provider was unavailable or its response could not be parsed. It is not a passing gate.
How do I get a result for scripts?
Use `openswarm review --json`. It returns a versioned verdict schema and suppresses the human-readable report.
Does local review require Linear?
No. Linear belongs to the optional task layer; local change review runs independently.
How are writes blocked when reviewing an untrusted PR?
Read-only mode withholds mutating tools. An adapter that cannot enforce it refuses to start that review.
How do I check the environment first?
Run `openswarm doctor` to inspect runtime, native dependencies and provider configuration.
Discussion
No questions or reviews yet.
Related
CLI toolsA code-review CLI and plugin for agents: reads a git diff and writes line-level comments with context
A skill and CLI for code review: a team of reviewer agents inspects changes independently, debates findings and produces one report
The CLI matches linter diagnostics to code changes and reports findings locally or through an approved review channel.
OpenCode plugin that turns a session into a team of agents led by an architect and runs the work through plan phases
Chorus convenes 2–4 AI reviewers from different CLIs to check a change before release, and plugs into agents as an MCP server.
A CLI and three skills that work through review-bot comments on a PR: assess findings, fix code, reply and wait for checks
README in short
The project includes a local task interface and optional pull-request maintenance commands. Verification can compare the head with its merge base and track pre-existing failures separately.