OpenSwarm

What does this agent do, and when should you use it?

OpenSwarm is a TypeScript and Node.js 22+ autonomous development orchestrator operated through a TUI, CLI, Discord, and a web dashboard. It takes work from Linear or a built-in SQLite tracker, filters it through DecisionEngine, and runs Worker and Reviewer pairs with optional Tester and Documenter stages in PairPipeline. Execution adapters cover Codex, OpenAI GPT, OpenRouter, Atlas Cloud, Ollama, LM Studio, and an opt-in Claude Code CLI fallback. The repository also includes a code entity registry, BS Detector, LanceDB long-term memory, and repository-scoped knowledge recall. It fits engineering teams willing to configure provider credentials, project paths, and verification commands in exchange for a self-hosted workflow spanning issue execution, review, and CI repair.

AutonomousRunner fetches Linear issues on a heartbeat, DecisionEngine applies scope, priority, and limit checks, then projectMapper resolves a project path before calling PairPipeline.run(). A Worker edits through the configured adapter, a Reviewer returns APPROVE, REVISE, or REJECT, and the loop can repeat before optional Tester and Documenter stages. openswarm review reviews working-tree changes; openswarm review --max splits a codebase into areas for reviewer subagents and can emit an audit report, Linear issues, JSON decisions, or SARIF; --fix repairs in isolated sandboxes and publishes a PR only after re-review and deterministic verification. openswarm fix detects npm, Cargo, or Python checks, groups failures by file, and reruns checks across repair rounds. The Code Registry writes functions, classes, and types to SQLite/FTS5, openswarm check --bs scans code-smell patterns, and completed-task outcomes are stored in LanceDB for later repository-specific prompt recall and search_memory queries.

1. An engineering team using Linear that wants scheduled issue selection, implementation, review, and issue-state updates in one workflow.
2. A team that needs PR review as a GitHub Actions merge gate, using the included composite action, JSON verdicts, or SARIF output.
3. A maintainer of a Node, Rust, or Python repository who wants openswarm fix to repair failing lint, typecheck, build, or test checks and rerun them.
4. A Discord-based development team that wants to dispatch work, inspect active tasks, control autonomous execution, and change providers with bot commands.
5. A developer who wants to use local Ollama or LM Studio models for coding workflows while retaining Codex, GPT, or OpenRouter options.

How do you install or deploy this agent?

Requires Node.js 22+, at least one configured LLM provider, and a native build toolchain for better-sqlite3 and @lancedb/lancedb. Install and start with:

npm install -g @intrect/openswarm
openswarm init
openswarm doctor
openswarm

The setup wizard can configure ChatGPT OAuth, OpenRouter, GPT, Ollama, LM Studio, or an authenticated claude CLI. For manual setup, first run openswarm auth login or set OPENROUTER_API_KEY for OpenRouter. Autonomous operation can additionally use Linear OAuth/API credentials and Discord bot credentials.

How do you use this agent?

Run openswarm init in the repository to manage so the wizard writes config.yaml and .env; then use openswarm start for the background daemon, or run one task with openswarm run "Fix the bug" -p ~/my-project. For a full local pipeline without the daemon, use openswarm exec "Run tests" --local --pipeline. Review current changes with openswarm review, and repair detected check failures with openswarm fix. openswarm dash opens the dashboard on port 3847.

What are this agent's strengths and limitations?

How does this agent compare with similar options?

Key facts side by side with the most closely related agents.

How does FollowAgents rate this agent?

Recent releases

Latest entries from the project's GitHub Releases. Notes are quoted from upstream as written, not rewritten or tested by FollowAgents.

1. v0.24.4 2026-09-29
   Release notes excerpt

   Added - A review of content this deployment already reviewed is replayed from a durable store instead of paying for the reviewer again. src/automation/reviewVerdictStore.ts keys a verdict on (kind, base, sha256(content digest)), the digest being every changed path paired with its content hash, and replays the stored outcome on a hit — from both the plain openswarm review path (reviewCommand.ts) and the publication hook (publicationReviewHook.ts). Measured over the recorded history (530 records, 512 carrying a verdict): 68 byte-identical pairs, 15 of them same-mode (8 direct→ …

   View on GitHub ↗
2. v0.24.2 2026-09-20
   Release notes excerpt

   Fixed - Reviewer salvage now preserves a real verdict (AGT-4484). When a reviewer exhausts its tool turns, the final no-tools turn explicitly requires Decision: approve, Decision: revise, or Decision: reject with concrete reasoning instead of returning a worker-status summary that the reviewer parser must discard.

   View on GitHub ↗
3. v0.24.1 2026-09-20
   Release notes excerpt

   Added - Cost-capped GitHub Action reviews. openswarm review --model <id> is now exposed by the CLI and the composite action forwards its optional model input through the same reviewed call chain. The action refuses as gate-not-run when an older installed package lacks the option, rather than silently falling back to an uncontrolled default model. The dogfood workflow pins deepseek/deepseek-v4-flash. - Backfill for pre-publication parked branches (AGT-4124). `openswarm drain-parks --path <repo> finds unowned NEEDS_HUMAN` rows, creates or …

   View on GitHub ↗

FAQ