Autonomous AI agent orchestrator — Codex, GPT, OpenRouter (any model), local models (Ollama/LM Studio), and Claude Code (
claude -p)
💬 Help shape OpenSwarm. Share feature ideas, vote on the roadmap, and ask questions in GitHub Discussions. The roadmap is built in the open — your feedback decides what ships next.
OpenSwarm orchestrates multiple AI agents as autonomous code workers. It picks up issues from Linear or a built-in local tracker, runs Worker/Reviewer pair pipelines, reports through a pluggable notifier (Discord, Slack, Telegram, webhook), and retains long-term memory via LanceDB. Workers run on OpenAI Codex/GPT, any OpenRouter model, local open-source models (Ollama, LM Studio), or Claude Code (claude -p, opt-in) — with cost-aware routing measured on an L0–L6 benchmark ladder.
Verified on real GitHub issues: the agentic harness solves SWE-bench Lite instances graded by the official harness. Hybrid mode — a frontier model diagnoses read-only, a lightweight model implements with a verification loop — resolved 3/3 attempted instances that every single lightweight model had failed, at a fraction of frontier-only cost. Workers also learn each repository over time: task outcomes are stored as per-repo knowledge and recalled into future prompts. (benchmark rubric & results)
npm install -g @intrect/openswarm
openswarm init # interactive setup wizard — provider auth + Linear OAuth + config
openswarm doctor # verify your environment (runtime, native deps, providers, ports)
openswarm # launches the TUI chatopenswarm init walks you through provider authentication, optional Linear OAuth (team/project picker), and writes a validated config.yaml. Prefer wiring a provider by hand? You need one first: openswarm auth login (ChatGPT OAuth, used by codex/gpt), openswarm auth login --provider openrouter (or export OPENROUTER_API_KEY=…), or just have an authenticated claude on PATH. Check what's wired with openswarm auth status, and diagnose any gaps with openswarm doctor.
The wizard asks three questions, detects what you already have, and writes the config for you:
- AI provider (worker/reviewer) — it auto-detects existing auth and offers inline login:
codex-responses— ChatGPT subscription via OAuth (Codex models, native loop) — easiest startcodex— externalcodexCLI ·openrouter— any model (API key/OAuth) ·gpt— OpenAI OAuthlmstudio/local— local servers, no account ·claude—claude -pCLI (opt-in fallback)
- Task backend —
localSQLite issue store (no account) orlinear(OAuth browser login or API key, then an arrow-key team → project picker for this repo) - Notification channel (optional) —
none/discord/slack/telegram/webhook
It then writes .env (secrets, chmod 600), config.yaml (validated), and — if you mapped a Linear project — openswarm.json (this repo → Linear team/project). Finally it prints next steps and can launch browser OAuth.
Re-running in a repo that already has
config.yamlis refused unless you pass--force, andinitrefuses to overwrite aconfig.yamlthat symlinks into the daemon's global config. For CI / non-interactive use,openswarm init --yeswrites a sample config only.
| Key | Action |
|---|---|
Tab |
Switch tabs (Chat / Projects / Tasks / Stuck / Issues / Logs) |
Enter |
Send message |
Shift+Enter |
Newline |
i |
Focus input |
Esc |
Exit input focus |
Ctrl+C |
Quit |
Status bar shows: provider · model · message count · cumulative cost
openswarm # TUI chat (default)
openswarm chat [session] # Simple readline chat
openswarm start # Start full daemon (requires config.yaml)
openswarm run "Fix the bug" -p ~/my-project # Run a single task
openswarm exec "Run tests" --local --pipeline # Execute via daemon
openswarm init # Interactive setup wizard (provider auth, Linear OAuth, config)
openswarm doctor # Diagnose environment (runtime, native deps, providers, ports)
openswarm validate # Validate config.yaml
# Code Registry & BS Detector
openswarm check --scan # Scan repo → register all entities
openswarm check src/foo.ts # File brief (entities, tests, risk)
openswarm check --bs # BS pattern scan (bad code smells)
openswarm check --stats # Registry statistics
openswarm check --high-risk # High-risk entities
openswarm check --search "name" # Full-text search
openswarm annotate "funcName" --deprecate "reason"
openswarm annotate "funcName" --tag "needs-refactor"
openswarm annotate "funcName" --warn "error/security: SQL injection"| Option | Description |
|---|---|
--path <path> |
Project path (default: cwd) |
--timeout <seconds> |
Timeout in seconds (default: 600) |
--local |
Execute locally without daemon |
--pipeline |
Full pipeline: worker + reviewer + tester + documenter |
--worker-only |
Worker only, no review |
-m, --model <model> |
Model override for worker |
Exit codes: 0 success · 1 failure · 2 timeout
For autonomous operation (Linear issue processing, Discord control, PR auto-improvement), you need a full config:
- Node.js >= 22
- At least one LLM provider:
- OpenAI Codex —
codex-responses(ChatGPT OAuth, native loop, no extra binary) is the smoothest start;codexdelegates to the external Codex CLI.openswarm auth loginhandles the ChatGPT OAuth - OpenRouter — any model;
OPENROUTER_API_KEYoropenswarm auth login --provider openrouter - OpenAI GPT —
openswarm auth login --provider gpt - Local — LM Studio (
lmstudio,:1234) or Ollama (local,:11434), auto-detected, no auth - Claude Code CLI (
claude -p) — opt-in fallback; an authenticatedclaudeon PATH
- OpenAI Codex —
- Native build toolchain —
better-sqlite3and@lancedb/lancedbare native modules. Prebuilt binaries cover common platforms; if yours lacks one,npm installbuilds from source and needspython3+ a C/C++ toolchain (build-essentialon Linux, Xcode Command Line Tools on macOS) - For autonomous mode only (optional): Linear — sign in with
openswarm auth login --provider linear(OAuth PKCE) or use an API key + team ID; Discord bot token (message content intent); GitHub CLI (gh) for CI monitoring
After the global install, run the wizard in the directory you want the daemon to manage — it writes everything for you:
openswarm init # writes config.yaml + .env (provider, task backend, notifications)
openswarm doctor # verify providers, native deps, portsSee What openswarm init sets up for the prompts. Prefer to edit by hand? config.yaml supports ${VAR} / ${VAR:-default} substitution (resolved from .env) and is validated with Zod. A minimal .env (the wizard writes only what your choices need):
LINEAR_API_KEY=your-linear-api-key # or: openswarm auth login --provider linear
LINEAR_TEAM_ID=your-linear-team-id
DISCORD_TOKEN=your-discord-bot-token # only if you chose the discord notifier
DISCORD_CHANNEL_ID=your-channel-id| Section | Description |
|---|---|
discord |
Bot token, channel ID, webhook URL |
linear |
API key, team ID |
github |
Repos list for CI monitoring |
agents |
Agent definitions (name, projectPath, heartbeat interval) |
autonomous |
Schedule, pair mode, role models, decomposition settings |
prProcessor |
PR auto-improvement schedule, retry limits, conflict resolver config |
adapter: codex # one of: codex · codex-responses · gpt · openrouter · lmstudio · local (default: codex)adapter accepts one of the six values below (validated by Zod). For a ChatGPT subscription, codex-responses is the smoothest first-run choice — it runs OpenSwarm's native loop over the Responses API with no extra binary. Switch at runtime via Discord, e.g. !provider codex-responses / !provider openrouter.
| Adapter | Backend | Models | Auth |
|---|---|---|---|
codex-responses |
OpenAI Responses API (native loop, no CLI binary) | gpt-5-codex (default), o3, o4-mini | ChatGPT OAuth |
codex |
OpenAI Codex CLI (delegated) | gpt-5-codex (default), o3, o4-mini | ChatGPT OAuth / codex CLI auth |
gpt |
OpenAI Chat API | gpt-4o (default), o3, … | OAuth PKCE |
openrouter |
OpenRouter API (native agentic loop) | any OpenRouter model — gpt-5, gemini-2.5, deepseek, glm, qwen, … | OPENROUTER_API_KEY or OAuth PKCE |
lmstudio |
LM Studio (OpenAI-compatible, local) | loaded LM Studio model (LMSTUDIO_MODEL) |
None |
local |
Ollama (local, auto-detected) | gemma, llama, qwen, mistral, … | None |
Claude Code (
claude -p) is supported as an opt-in fallback (and powers theclaude -pchat path) — install theclaudeCLI and authenticate it;openswarm initandopenswarm doctordetect it. It is not a selectableadapter:value.
The openrouter adapter runs OpenSwarm's own agentic tool loop (read/search/edit/bash with verification guards), enables ZDR (data_collection: deny) for non-OpenAI models, and applies Anthropic prompt caching automatically. Local backends are auto-detected on standard ports (Ollama :11434, LM Studio :1234); use lmstudio for a dedicated LM Studio endpoint (LMSTUDIO_BASE_URL, default http://localhost:1234).
Per-role adapter overrides (each role may pick its own valid adapter + model):
autonomous:
defaultRoles:
worker:
adapter: codex-responses
model: gpt-5-codex
reviewer:
adapter: openrouter
model: anthropic/claude-sonnet-4autonomous:
defaultRoles:
worker:
model: gpt-5-codex
escalateModel: openai/gpt-5 # escalate after repeated review failures
escalateAfterIteration: 3
timeoutMs: 1800000
reviewer:
model: gpt-5-codex
timeoutMs: 600000
tester:
enabled: false
documenter:
enabled: false
auditor:
enabled: falseWith the global install, the openswarm CLI manages the daemon directly — no repo or npm run scripts needed:
openswarm start # start the daemon in the background
openswarm start --foreground # run attached (logs stream to the terminal)
openswarm status # pid, uptime, log path
openswarm stop # stop the daemon
openswarm dash # open the web dashboard (:3847)From source / development (contributors): clone the repo and use the
npm run …scripts (npm run dev,npm start,npm run service:installfor a macOS launchd service,docker compose up -d). See CONTRIBUTING.md.
┌──────────────────────────┐
│ Linear API │
│ (issues, state, memory) │
└─────────────┬────────────┘
│
┌─────────────────────┼─────────────────────┐
│ │ │
v v v
┌──────────────────┐ ┌──────────────────┐ ┌──────────────────┐
│ AutonomousRunner │ │ DecisionEngine │ │ TaskScheduler │
│ (heartbeat loop) │─>│ (scope guard) │─>│ (queue + slots) │
└────────┬─────────┘ └──────────────────┘ └────────┬─────────┘
│ │
v v
┌──────────────────────────────────────────────────────────────┐
│ PairPipeline │
│ ┌────────┐ ┌──────────┐ ┌────────┐ ┌─────────────┐ │
│ │ Worker │──>│ Reviewer │──>│ Tester │──>│ Documenter │ │
│ │(Adapter│<──│(Adapter) │ │(Adapter│ │ (Adapter) │ │
│ └───┬────┘ └──────────┘ └────────┘ └─────────────┘ │
│ │ ↕ StuckDetector │
│ ┌───┴────────────────────────────────────────────────────┐ │
│ │ Adapters: Codex | GPT | OpenRouter | Local (Ollama) │ │
│ └────────────────────────────────────────────────────────┘ │
└──────────────────────────────────────────────────────────────┘
│ │ │
v v v
┌──────────────┐ ┌──────────────────┐ ┌──────────────────┐
│ Discord Bot │ │ Memory (LanceDB │ │ Knowledge Graph │
│ (commands) │ │ + Xenova E5) │ │ (code analysis) │
└──────────────┘ └──────────────────┘ └────────┬─────────┘
│
┌────────┴─────────┐
│ Code Registry │
│ (SQLite + FTS5) │
│ + BS Detector │
└──────────────────┘
- Multi-Provider Adapters — Pluggable adapter system: OpenAI Codex/GPT, OpenRouter (any model, native agentic loop), local models (Ollama, LM Studio), and Claude Code (
claude -p, opt-in) with runtime provider switching - Code Registry — SQLite-backed entity registry tracking every function/class/type across 8 languages, with complexity scoring, test mapping, and risk assessment
- BS Detector — Built-in static analysis engine that detects bad code patterns (empty catch, hardcoded secrets,
as any, etc.) with pipeline guard integration - Autonomous Pipeline — Cron-driven heartbeat fetches Linear issues, runs Worker/Reviewer pair loops, and updates issue state automatically
- Worker/Reviewer Pairs — Multi-iteration code generation with automated review, testing, and documentation stages
- Decision Engine — Scope validation, rate limiting, priority-based task selection, and workflow mapping
- Cognitive Memory — LanceDB vector store with Xenova/multilingual-e5-base embeddings for long-term recall across sessions
- Repo Knowledge Loop — workers learn each repository over time: task outcomes (success patterns, review-rejection pitfalls) are stored per-repo and recalled into the next worker prompt
- SWE-bench Verified — the agentic harness solves real SWE-bench Lite issues, graded by the official harness; hybrid mode (frontier diagnosis + lightweight implementer) resolved 3/3 attempted instances (benchmarks/RUBRIC.md)
- Knowledge Graph — Static code analysis, dependency mapping, impact analysis, and file-level conflict detection across concurrent tasks
- Discord Control — Full command interface for monitoring, task dispatch, scheduling, provider switching, and pair session management
- Rich TUI Chat — Claude Code inspired terminal interface with tabs, streaming responses, and geek-themed loading messages
- Dynamic Scheduling — Cron-based job scheduler with Discord management commands
- PR Auto-Improvement — Monitors open PRs, auto-fixes CI failures, auto-resolves merge conflicts, and retries until all checks pass
- Long-Running Monitors — Track external processes (training jobs, batch tasks) and report completion
- Web Dashboard — Real-time pipeline stages, cost tracking, worktree status, and live logs on port 3847
- Pace Control — 5-hour rolling window task caps, per-project limits, turbo mode, exponential backoff on failures
- i18n — English and Korean locale support
Linear (Todo/In Progress)
→ Fetch assigned issues
→ DecisionEngine filters & prioritizes
→ Resolve project path via projectMapper
→ PairPipeline.run()
→ Worker generates code (via the configured adapter)
→ Reviewer evaluates (APPROVE/REVISE/REJECT)
→ Loop up to N iterations
→ Optional: Tester → Documenter stages
→ Update Linear issue state (Done/Blocked)
→ Report to Discord
→ Save to cognitive memory
Hybrid retrieval: 0.55 × similarity + 0.20 × importance + 0.15 × recency + 0.10 × frequency
Memory types: belief · strategy · user_model · system_pattern · constraint
Background: decay, consolidation, contradiction detection, distillation.
Repo knowledge loop — every completed task writes repo-scoped knowledge
(success → system_pattern with files changed + approach, review rejection →
constraint pitfall), and the next task on the same repo recalls the most
relevant entries into the worker prompt as a "Repository Knowledge" section.
Workers get better at a codebase the more they work on it.
benchmarks/ contains a difficulty ladder for routing models by measured
capability — synthetic L0–L5 tasks with deterministic grading, and L6 = real
GitHub issues (SWE-bench Lite) solved by the OpenSwarm harness and graded by
the official swebench harness. Headline: hybrid mode (frontier read-only
diagnosis + lightweight implementer with a verification loop) resolved 3/3
attempted instances that every single lightweight model had failed. See
benchmarks/RUBRIC.md for the rubric, measured results,
and the harness defects the benchmark uncovered.
| Command | Description |
|---|---|
!dev <repo> "<task>" |
Run a dev task on a repository |
!dev list |
List known repositories |
!tasks |
List running tasks |
!cancel <taskId> |
Cancel a running task |
| Command | Description |
|---|---|
!status |
Agent and system status |
!pause <session> |
Pause autonomous work |
!resume <session> |
Resume autonomous work |
!log <session> [lines] |
View recent output |
| Command | Description |
|---|---|
!issues |
List Linear issues |
!issue <id> |
View issue details |
!limits |
Agent daily execution limits |
| Command | Description |
|---|---|
!auto |
Execution status |
!auto start [cron] [--pair] |
Start autonomous mode |
!auto stop |
Stop autonomous mode |
!auto run |
Trigger immediate heartbeat |
!approve / !reject |
Approve or reject pending task |
| Command | Description |
|---|---|
!pair |
Pair session status |
!pair start [taskId] |
Start a pair session |
!pair run <taskId> [project] |
Direct pair run |
!pair stop [sessionId] |
Stop a pair session |
!pair history [n] |
View session history |
!pair stats |
View pair statistics |
| Command | Description |
|---|---|
!schedule |
List all schedules |
!schedule run <name> |
Run a schedule immediately |
!schedule toggle <name> |
Enable/disable a schedule |
!schedule add <name> <path> <interval> "<prompt>" |
Add a schedule |
!schedule remove <name> |
Remove a schedule |
| Command | Description |
|---|---|
!ci |
GitHub CI failure status |
!provider <codex|codex-responses|openrouter|gpt|lmstudio|local> |
Switch CLI provider at runtime |
!codex |
Recent session records |
!memory search "<query>" |
Search cognitive memory |
!help |
Full command reference |
src/
├── index.ts # Entry point
├── cli.ts # CLI entry point (run, exec, chat, init, validate, start)
├── cli/ # CLI subcommand handlers
│ └── promptHandler.ts # exec command: daemon submit, auto-start, polling
├── core/ # Config, service lifecycle, types, event hub
├── adapters/ # Provider adapters (codex, codex-responses, gpt, openrouter, local, lmstudio), agentic loop
├── agents/ # Worker, reviewer, tester, documenter, auditor
│ ├── pairPipeline.ts # Worker → Reviewer → Tester → Documenter pipeline
│ ├── agentBus.ts # Inter-agent message bus
│ └── cliStreamParser.ts # Claude CLI output parser
├── orchestration/ # Decision engine, task parser, scheduler, workflow
├── automation/ # Autonomous runner, cron scheduler, PR processor
├── memory/ # LanceDB + Xenova embeddings cognitive memory
├── knowledge/ # Code knowledge graph (scanner, analyzer, graph)
├── registry/ # Code entity registry, BS detector, entity scanner
├── issues/ # Local issue tracker (SQLite + GraphQL + Kanban UI)
├── discord/ # Bot core, command handlers, pair session UI
├── linear/ # Linear SDK wrapper, project updater
├── github/ # GitHub CLI wrapper for CI monitoring
├── support/ # Web dashboard, planner, rollback, git tools
├── locale/ # i18n (en/ko) with prompt templates
└── __tests__/ # Vitest test suite
| Path | Description |
|---|---|
~/.openswarm/ |
State directory (memory, codex, metrics, workflows) |
~/.openswarm/registry.db |
Code entity registry (SQLite) |
~/.openswarm/issues.db |
Local issue tracker (SQLite) |
~/.claude/openswarm-*.json |
Pipeline history and task state |
config.yaml |
Main configuration |
dist/ |
Compiled output |
| Category | Technology |
|---|---|
| Runtime | Node.js 22+ (ESM) |
| Language | TypeScript (strict mode) |
| Build | tsc |
| Agent Execution | Claude Code, OpenAI GPT/Codex, Ollama/LMStudio/llama.cpp |
| Local DB | better-sqlite3 (WAL mode, FTS5) |
| Task Management | Linear SDK (@linear/sdk) |
| Communication | Discord.js 14 |
| Vector DB | LanceDB + Apache Arrow |
| Embeddings | Xenova/transformers (multilingual-e5-base, 768D) |
| Scheduling | Croner |
| Config | YAML + Zod validation |
| Linting | oxlint |
| Testing | Vitest |
- License — relicensed to MIT (was GPL-3.0)
- Docs — README overhauled for first-time users (
openswarm initwalkthrough, accurate adapter registry, latest-build models) and contributor health files added (CONTRIBUTING, Code of Conduct, Security policy, PR template)
- Interactive
openswarm initwizard — Linear OAuth (PKCE) sign-in with arrow-key team/project picker, provider auto-detection, and a validatedconfig.yaml(INT-1808) openswarm doctor— one-shot environment diagnostics: Node version, native modules, provider CLIs, ports, and config discovery- Linear OAuth login —
openswarm auth login --provider linear(PKCE, no API-key entry) - CLI polish — ASCII banner and colored output (NO_COLOR / non-TTY aware)
- Autonomy hardening — dependency-order gating + Backlog parking (INT-1809), daemon self-modify guards (INT-1810),
jobProfilespartial roles carried through to runtime (INT-1812), and aninitsymlink guard that refuses to overwrite the daemon's global config - Fix — codex adapter
--full-auto→--sandbox workspace-write(codex 0.137 deprecation) (INT-1699)
- Native Codex Responses-API adapter (
codex-responses) — ChatGPT OAuth, no CLI binary required; live model discovery via the OAuth backend - Linear-optional autonomy —
ITaskSourceabstraction + local SQLite task source; the autonomous runner no longer requires Linear - Notifier abstraction — Discord / Slack / Telegram / webhook
- Agentic loop tools —
web_fetch+web_search - Planner cockpit TUI —
/plandecompose → approve → dispatch - Loop maturity (INT-1679) — bad-edit guard + reflection self-repair loop
- Conflict-free concurrency (INT-1610) — blocker/dependency ordering for parallel workers; worker instructions + actions logged to issue comments
- Benchmarks (L0–L6) — difficulty rubric, model-routing benchmark, and a real SWE-bench harness
- Repo knowledge loop — workers learn each repository across tasks (per-repo success patterns + review-rejection pitfalls recalled into prompts)
- OpenRouter agentic adapter — native tool loop with harness hardening from SWE-bench findings
- LM Studio adapter with auto model selection
- CLI —
openswarm dash,--tree/--ciflags forcheck
- Code Registry:
openswarm check --scanscans repo, registers 1000+ entities across 8 languages (TS, Python, Go, Rust, Java, C, C++, C#) with test mapping, complexity scoring, and risk assessment - BS Detector:
openswarm check --bs— built-in static analysis for bad code patterns, pipeline guard integration - Local Model Support: Ollama, LMStudio, llama.cpp via single
localadapter with auto-detection - GPT Adapter: OpenAI models via OAuth PKCE flow
- Local Issue Tracker: SQLite + GraphQL + Kanban web UI at
:3847/issues - CLI:
openswarm check,openswarm annotatecommands
openswarmwithout arguments now launches TUI chat directly
- Security: patched lodash, picomatch, rollup, undici, yaml vulnerabilities
- Published as
@intrect/openswarmon npm - Extracted
@intrect/claude-driveras standalone zero-dependency package - Autonomous runner hardening and multi-project orchestration
- Task-state rehydration from Linear comments
--verboseflag for detailed execution logging- Codex adapter: dropped o-series model override
- Initial release
- Worker/Reviewer pair pipeline
- Claude Code CLI + Codex CLI adapters
- Discord bot control
- Linear integration
- LanceDB cognitive memory
- Web dashboard (port 3847)
- Rich TUI chat interface
If the chat TUI shows each Hangul (or other multibyte) character twice —
이이렇렇게 쓰쓰이는것 — while ASCII characters look fine, the cause is almost
always client-side local / predictive echo in the mobile SSH app drawing an
extra copy of wide characters. The keystroke reaches OpenSwarm once; the terminal
paints it twice.
Fix it in the SSH client:
-
Termius → Host/Terminal settings → turn Local Echo (a.k.a. predictive echo) off, and ensure the encoding is UTF-8.
-
Confirm the server side is fine by running with diagnostics:
OPENSWARM_DEBUG_INPUT=1 openswarm chat
Type a few Korean characters, then inspect
~/.openswarm/input-debug.log. If a single keypress logs one code point (cp=[51060]) but you saw two glyphs, the doubling is terminal echo (client-side). If it logs the code point twice in one event, it's an app-level issue — please attach the log to a bug report.
Contributions are welcome — OpenSwarm is MIT-licensed and accepts pull requests from anyone. See CONTRIBUTING.md for development setup, the local check gates, branch/commit conventions, and the PR process. By participating you agree to the Code of Conduct.
- 🐛 Report a bug
- 💡 Share an idea — the roadmap is built in the open
- 🔧 Fork the repo, branch from
main, and open a PR (CI runs lint → typecheck → build → test) - 🔒 Found a security issue? See SECURITY.md — please don't file it publicly
MIT © Heewon Oh
