OpenClaw + crewswarm

OpenClaw is a strong surface.
crewswarm runs the engineering crew.

OpenClaw is good at being the front door: desktop apps, messaging, and a broad assistant surface.
crewswarm handles the heavier engineering workflow behind it: planning, delegation, coding, QA, fixes, and shipping.

How they work together ↓ Full comparison
Better together

What OpenClaw Does Well

OpenClaw is a mature personal AI assistant platform. It has real strengths — and crewswarm is designed to complement them, not replace them.

Desktop & mobile apps

Native macOS, Windows, iOS, and Android apps. A polished UI that millions of users already know.

Messaging channels

Telegram, WhatsApp, Discord, iMessage, Slack, Signal, and more. Talk to your AI from anywhere.

Massive community

Large community, active development, and an established plugin ecosystem. A proven platform.

Plugin system

Extensible via plugins published to ClawHub or npm. One command to install new capabilities.

What crewswarm Adds

OpenClaw is a surface. crewswarm is the system behind the surface: specialist agents, multiple engine lanes, shared context, and a PM loop that plans, delegates, evaluates, and iterates.

22 specialist agents

Dedicated agents for coding, QA, security, frontend, backend, docs, git, architecture, ML, SEO, and more. Each with their own model and tools.

6 coding engines

Claude Code, Cursor, Codex, Gemini CLI, OpenCode, and crew-cli. Agents pick the right engine for the task.

Autonomous PM loop

Describe a feature once. The PM agent plans it, dispatches to specialists, evaluates results, and iterates until it ships.

Shared memory & context

All agents share project state, decisions, and handoff context. No agent works blind. No repeated explanations.

Use them together

Use OpenClaw as the front door — chat from your phone, desktop, or any channel. crewswarm does the heavy lifting behind the scenes: planning, coding, testing, and shipping with a full specialist crew.

openclaw plugins install crewswarm-openclaw-plugin

crewswarm works without OpenClaw

OpenClaw is one of many surfaces. crewswarm runs independently with its own dashboard, Vibe IDE, crew-cli, Telegram, and WhatsApp — no OpenClaw required.

💻
Dashboard

Web UI at localhost:4319

🎨
Vibe IDE

Monaco editor + agent chat

⌨️
crew-cli

Terminal-first workflow

Migrating from OpenClaw?

The installer automatically detects ~/.openclaw/openclaw.json and migrates your API keys into crewswarm. No manual config copying. OpenClaw stays installed — use it as a surface or uninstall it later.

# 1. Install crewswarm (keeps OpenClaw intact)
$ git clone https://github.com/crewswarm/crewswarm && cd crewswarm
$ bash install.sh
✓ Found OpenClaw config — migrated 4 API keys
# 2. Start — your keys are already configured
$ npm start
# 3. Done. Dashboard, Vibe, CLI, Telegram, WhatsApp all ready
Why local-first

The Case for Running AI on Your Machine

Cloud AI orchestration platforms route your code through third-party servers, add subscription costs, and lock you into a single provider. There is a better way.

Privacy by default

Your source code never leaves your machine. API keys are stored locally, not on any third-party server. Audit everything yourself.

No vendor lock-in

Swap models and providers freely. Use Anthropic today, switch to Groq tomorrow, run Ollama offline. One config change, zero migration.

No subscription fees

Bring your own API keys and pay providers directly. No middleman markup, no per-seat pricing, no surprise invoices.

Multi-engine orchestration

Run Claude Code, Cursor, crew-cli, Gemini CLI, and OpenCode simultaneously. A PM loop plans and delegates across all engines.

Offline capable

Works without internet when paired with local models via Ollama or LM Studio. Ideal for air-gapped or privacy-sensitive environments.

Fully open source

MIT licensed. Read every line, fork it, self-host it, extend it. No telemetry, no tracking, no proprietary backend.

crewswarm vs. Cloud Platforms vs. Single-Tool CLIs

A side-by-side look at the three approaches to AI-assisted development.

Capability crewswarm Cloud Platforms Single-Tool CLIs
Code privacy Local-first — code never uploaded Code sent to third-party servers Varies by tool
API key storage Local only — your machine, your keys Stored on provider servers Local
Subscription cost Free — bring your own API keys $20–$200+/mo per seat Free or pay-per-use
Vendor lock-in None — swap providers any time Tied to one platform Tied to one model vendor
Multi-engine support Claude, Cursor, crew-cli, Codex, Gemini, OpenCode Usually one engine Single engine only
Autonomous PM loop ROADMAP.md → plan → delegate → ship → repeat Manual task management No orchestration
Agent count 20+ specialized agents Varies 1 agent
Persistent memory brain.md + shared memory + JSONL history Cloud-managed context Session-only
Offline mode Yes — local models via Ollama / LM Studio No — requires internet Some support local models
Docker isolation Optional secure sandbox (AppArmor + firewall) Server-side isolation No sandboxing
Dashboard UI Full web dashboard + Vibe browser IDE Web UI included Terminal only
LLM providers 12+ (OpenAI, Anthropic, Groq, Fireworks, OpenRouter, Cerebras, DeepSeek, xAI, etc.) 1–3 typically 1
MCP integration Cursor, Claude Code, OpenCode Varies Some support
Messaging bridges Telegram + WhatsApp Slack / Teams common None
License MIT — fully open source Proprietary Varies
How it works

From Idea to Shipped Code in One Command

crewswarm replaces the manual cycle of prompting, reviewing, and re-prompting across scattered tools.

Describe the idea

Write a requirement in plain language. The PM agent turns it into a roadmap.

Agents plan and build

Domain PMs delegate tasks to the best engine for each job — Claude for architecture, Codex for implementation, Gemini for breadth.

Review and ship

The judge agent evaluates output. Good work ships. Bad work gets retried. You stay in control.

FAQ

Frequently Asked Questions

Is crewswarm free?

Yes. crewswarm is fully open source under the MIT license. You bring your own API keys and pay providers directly — no subscription fees, no middleman markup, no per-seat pricing.

Can I use crewswarm without internet?

Yes. Pair crewswarm with local models through Ollama or LM Studio and run agents entirely offline. This is ideal for air-gapped environments, sensitive codebases, or travel.

How does crewswarm compare to using Claude Code alone?

Claude Code is one of the engines crewswarm can orchestrate. The difference is scope:

  • Single CLI — one model, one task at a time, session-only memory.
  • crewswarm — multiple engines in parallel, autonomous PM loop, persistent memory, domain-aware planning, and a web dashboard.

Think of it as the difference between a single developer and a full engineering team.

Is my code safe with crewswarm?

Yes. crewswarm is local-first — your source code never leaves your machine. API keys are stored locally. For additional hardening, enable Docker isolation which adds read-only filesystem, AppArmor profiles, network firewall rules, and non-root execution. Read the full security guide.

What LLM providers does crewswarm support?

OpenAI, Anthropic, Groq, Fireworks, OpenRouter, Cerebras, DeepSeek, xAI (Grok), Mistral, Perplexity, Google (Gemini), and any OpenAI-compatible API. Switch providers with a single config change.

Can I self-host crewswarm?

That is the default. crewswarm runs entirely on your machine or your own server. Deploy to any cloud (AWS, GCP, DigitalOcean), bare metal, or localhost. No external dependencies, no telemetry, no phone-home behavior.

What makes crewswarm different from other AI coding tools?

Most tools give you one model behind a subscription. crewswarm gives you:

  • Multi-engine orchestration — six coding engines running simultaneously
  • An autonomous PM loop that plans, delegates, evaluates, and iterates
  • Persistent shared memory across all agents
  • A real control-plane dashboard and browser IDE
  • Full local ownership — open source, no cloud dependency
Already using OpenClaw?

Use crewswarm from inside OpenClaw

The official crewswarm plugin gives every OpenClaw agent access to your local crew. Dispatch tasks, poll results, and list agents — all without leaving OpenClaw.

Agent Tools

crewswarm_dispatch — send a task to any crew agent and wait for the result.
crewswarm_agents — list all 22 available agents.
crewswarm_status — poll a running task.

Slash Command

/crewswarm crew-coder "Add auth middleware"
Works from any OpenClaw channel — Telegram, WhatsApp, Discord, iMessage, or the desktop app.

Gateway RPC

Programmatic access via crewswarm.dispatch, crewswarm.status, and crewswarm.agents RPC methods.

openclaw plugins install crewswarm-openclaw-plugin

No LLM keys are shared — crewswarm uses its own providers. The only shared secret is the RT auth token. View on npm · Source & docs

Try crewswarm in 5 Minutes

One command. No sign-up. No subscription. Just clone, install, and start building.

git clone https://github.com/crewswarm/crewswarm && cd crewswarm && bash install.sh

Open source · MIT license · Multi-engine · Local-first · No subscriptions