Open Swarm
A local desktop mission control for running many coding agents in parallel on one pannable canvas.
- Source repo
- openswarm-ai/openswarm
- Stars
- ★ 826
- Last updated
- 2d ago
- License
- NOASSERTION
- Primary language
- JavaScript
- FA score
- Insufficient evidence
At a glance
- Works with
- Platform-specificClaude APIClaude Code (Partial support)
- You'll need
- Typical use
- Developers running several features at once: give each feature its own agent in a separate git worktree and watch them all on one canvas.
- Main limitation
- Core execution depends on claude-agent-sdk and Anthropic models/keys; moving to another model provider means writing your own adapter, as no multi-provider path is documented.
- Website
- openswarm.com ↗ set on GitHub
- Maintenance
- Commits in the last 30 dayslast commit 2026-11-18latest release v1.8.0 (2026-10-11)
- Source review
- Insufficient evidence 8 safety controls not found
What does this agent do, and when should you use it?
Open Swarm is a locally-running orchestrator that manages multiple coding agents side by side. It ships as an Electron shell wrapping a React/TypeScript frontend on port 3000 and a FastAPI backend on port 8324, which talk over REST (/api/*) and WebSockets (/ws/*). The backend's Agent Manager drives each session through claude-agent-sdk and persists state as JSON files. Every agent works inside its own git worktree and branch, and every tool call is gated behind a human approval step. Nothing is relayed through a cloud backend or telemetry, but you supply your own Anthropic API key and pay for model usage.
The frontend renders a spatial dashboard: an infinite canvas where agent cards, view cards and embedded browser cards can be dragged and arranged, with multiple dashboards for different workspaces. The Agent Chat page streams tokens over WebSockets, tracks USD cost per session, and keeps history across restarts. Each tool request raises a Human-in-the-Loop approval that you can approve or deny individually or batch-handle from the dashboard, with per-tool policies (always allow, ask, deny). Editing an earlier message forks the conversation so you can move between branches. Five built-in modes (Agent, Ask, Plan, View Builder, Skill Builder) plus custom modes define system prompts and tool restrictions, and prompt templates are invoked inline with / slash commands. The Skills library syncs to ~/.claude/skills/ and can install from the Anthropic skills marketplace; the Tools library configures MCP servers over stdio, HTTP or SSE with automatic tool discovery, browses the MCP registry and Google's catalog, and includes Google Workspace OAuth. Views/Outputs produce HTML/JS/CSS artifacts rendered in iframes with vibe coding, a Python executor and auto-run. Git worktree isolation gives each agent its own branch, and a Diff Viewer shows uncommitted changes without leaving the app.
- Developers running several features at once: give each feature its own agent in a separate git worktree and watch them all on one canvas.
- Teams that need to sign off on agent actions: file writes and command executions funnel into a single approval queue, batch-handled with Shift+A / Shift+D.
- Exploration before execution: use Plan or Ask mode to get a proposal without touching code, then switch back to Agent mode to implement.
- Users who repeat the same workflows: encode them as prompt templates with structured input fields and call them with
/in the chat box. - Technical users extending tool reach: wire MCP servers or Google Workspace (Gmail, Calendar, Drive) into agents through the Tools library.
- Anyone who changes direction mid-session: edit an earlier message to fork a branch and compare approaches without losing the original thread.
Key setup facts
Pulled from the install and usage notes below. The project README has the current values.
- Ports
8324·3000- Environment variables
GOOGLE_OAUTH_CLIENT_IDGOOGLE_OAUTH_CLIENT_SECRETBACKEND_PORT- Config files
backend/.env.examplebackend/.env- Runtime
- Python 3.13 · Node.js 18+
- Install notes cover
- Windows · macOS · Linux
How do you install or deploy this agent?
Option 1 — download the desktop build (currently macOS only):
https://github.com/openswarm-ai/openswarm/releasesGrab the latest release from GitHub Releases. No separate Python install is needed; the desktop package bundles a standalone Python 3.13 runtime. Windows and Linux builds are documented as planned but not yet available.
Option 2 — run the development setup from source. Prerequisites: Python 3.11+, Node.js 18+, Git.
git clone https://github.com/openswarm-ai/openswarm.git
cd openswarm
bash run.shThis starts the backend (port 8324), frontend (port 3000) and the Electron shell together. You can also run services individually:
bash backend/run.sh # API at http://localhost:8324 — docs at /docs
bash frontend/run.sh # App at http://localhost:3000The config file to copy is backend/.env.example to backend/.env; the Anthropic API key is not set there but in the in-app Settings page.
How do you use this agent?
On first launch, open the in-app Settings page and enter your Anthropic API key — it is required for normal use.
Create an agent card on the canvas and assign it a workspace; the agent begins work in its own git worktree and branch. Send a message in Agent Chat and the reply streams back token by token while a per-session USD cost counter updates.
When an agent wants to run a tool, a pending request appears on the dashboard:
Shift+A approve all pending requests
Shift+D deny all pending requestsCommon keyboard shortcuts:
D go to Dashboard
T go to Templates
1 – 9 open agent by position
? show shortcuts helpType / in the chat input to invoke prompt templates and skills. To add external tool reach, configure MCP servers (stdio, HTTP or SSE) on the Tools page and set GOOGLE_OAUTH_CLIENT_ID / GOOGLE_OAUTH_CLIENT_SECRET for Google Workspace OAuth. Ports and keys can be adjusted in backend/.env, for example BACKEND_PORT (default 8324).
What are this agent's strengths and limitations?
- Each agent gets its own git worktree and branch, so parallel workstreams don't collide, and the built-in Diff Viewer shows uncommitted changes in-app.
- All agents' tool requests land in one approval queue with per-request and batched (Shift+A / Shift+D) handling, plus per-tool policies of always allow, ask or deny.
- Fully local execution: the README states there is no cloud relay, no telemetry and no third-party backend, so sessions and cost data stay on your machine.
- Message branching: edit any earlier message to fork the conversation and move between alternative approaches without losing context.
- Tool integrations are MCP-native (stdio, HTTP, SSE) with automatic tool discovery and browsable MCP and Google registries.
- The desktop package bundles a standalone Python 3.13 runtime, so end users don't need Python preinstalled.
- Core execution depends on claude-agent-sdk and Anthropic models/keys; moving to another model provider means writing your own adapter, as no multi-provider path is documented.
- Official releases are macOS-only today; Windows and Linux builds are explicitly listed as planned but unavailable, leaving non-macOS users on the source route.
- Running it requires a paid Anthropic API key billed per use — the software is free, but model cost is not included.
- Source setup means juggling Python 3.11+, Node.js 18+ and Git, and optionally Google OAuth credentials for Workspace integration.
- License labeling looks inconsistent: README badge and text say MIT while repository metadata says AGPL-3.0, so confirm the actual terms before adopting.
How does this agent compare with similar options?
Key facts side by side with the most closely related agents.
| Agent | Source review | Form / cost | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|---|
| Open Swarm This agent | Insufficient evidence | — | ★ 826 | 2d ago | JavaScript | Claude API |
| DeterminFlow | 73 · Some gaps | Desktop appFree + model costs | ★ 979 | 2mo ago | Python | — |
| Neuron AI — Agentic Framework for PHP | 69 · Some gaps | Library / SDKFree + model costs | ★ 2.2k | 1d ago | PHP | OpenAI API · Claude API |
| Synapse AI — Multi-Agent Orchestration Platform | 58 · Major gaps | CLIFree + model costs | ★ 343 | 3d ago | Python | OpenAI API · Claude API |
How does FollowAgents rate this agent?
- Not found in source: least-privilege scopingGrant only what the task needs: a dedicated account or read-only token, scoped to specific directories and repos.
- Not found in source: confirmation before actingTurn on (or add) a confirmation step before it acts, and try it in a sandbox or test environment before real data.
- Not found in source: data-flow disclosureWatch which external services it contacts (proxy or firewall logs) and keep sensitive data out until you know where it goes.
- Not found in source: sensitive-data handlingUse dedicated, low-privilege, revocable API keys — never production credentials — and keep secrets out of logs.
- Not found in source: dependency securityPin versions and run a dependency audit (npm audit, pip-audit) before installing; prefer running it in a container.
- Not found in source: disclosed external effectsEstablish which external systems it writes to, sends to or changes, and verify with test accounts or repos before production.
- Not found in source: rollback or recovery pathBack up first, or work on a git branch or snapshot, so its changes can be undone.
- Not found in source: verifiable attributionInstall from the official repo or registry and check the publisher and URL to avoid look-alike packages.
- The packet only establishes that this repository stores signed builds. It does not include the Agent's main source, behavior, or operating instructions, so its actual capabilities and risks cannot be assessed.
Recent releases
Latest entries from the project's GitHub Releases. Notes are quoted from upstream as written, not rewritten or tested by FollowAgents.
-
Release notes excerpt
1.8.1-exp.5: Your work carries on through more kinds of trouble, and drafts, chats and the board hold steady. New - A reply that never starts, or goes quiet partway, is caught and carries on by itself on every provider. One chat's trouble no longer spills into your other chats. - Messages between agents wait their turn and are never lost or sent twice, and a chat that is waiting on another chat no longer shows as done: the status pill says it is waiting on a chat. …View on GitHub ↗ -
v1.8.0 1.8.0
-
v1.7.11 OpenSwarm 1.7.11
FAQ
Is Open Swarm open source?
Is Open Swarm still maintained?
Who makes Open Swarm?
What is Open Swarm's official website?
Thanks — we use this to improve the page.