// the take
SwarmClaw is a self-hosted, Node/TypeScript runtime for running multiple AI agents that can delegate to each other and to CLI coding tools (Claude Code, Codex, Gemini CLI, etc.), with memory, scheduling, and a UI for org-chart-style agent teams. It's aimed at people who want a local alternative to LangChain-style orchestration or a dashboard on top of tools like Claude Code, rather than people who just want a single chat agent.
Provider abstraction covers 24+ LLM backends (local Ollama/LM Studio through hosted Claude/GPT/Gemini/OpenRouter) behind one config surface, so you're not locked into a single vendor. MCP client support means it plugs into the growing MCP tool ecosystem instead of reinventing tool integrations. Delegation to real coding-agent CLIs (Claude Code, Codex, OpenCode) is a practical bridge rather than reimplementing coding capability from scratch. Deploy story is decent: multi-arch GHCR images plus ready-made Render/Fly/Railway configs lower the bar for actually running this somewhere besides a laptop.
Scope has crept well past 'agent runtime': crypto wallets with agent-held keys and autonomous transaction signing, a social network (SwarmFeed), and a task marketplace (SwarmDock) are all bundled into the same project that also runs unattended heartbeat loops — combining autonomous execution with wallet access is a real risk surface for a project this size (703 stars). The changelog shows repeated fixes to credential secret handling and decryption across several recent versions, which suggests the credential storage layer has been shaky rather than solved once. The macOS desktop build's code-signing/notarization gap has been open release after release, so the 'one-click installer' path has a known broken trust story on the platform most non-technical users would pick. With this much surface area (wallets, social, marketplace, multi-agent orchestration, structured sessions) maintained by what looks like a small team, expect any one subsystem to be less battle-tested than a tool that does one of these things well.
We read the README, the directory tree and a key source file in November 2026. Nobody pays to be listed. How we judge →