Cowork and Claude Code share one engine, OpenClaw is the real fork
Verified September 2, 2026.
Originally published August 10, 2026.
Short answer: if the work is a codebase, use Claude Code. If it is files, documents and inboxes, use Cowork. Pick OpenClaw only when you want to own the host and choose the model yourself.
| Claude Cowork | Claude Code | OpenClaw | |
|---|---|---|---|
| Best for | Files, docs, non-code work | Codebases, commits, PRs | An always-on assistant in your chat apps |
| Runs on | Claude desktop, web, mobile | Terminal, IDE, desktop, web | Your machine: macOS, Linux, Windows, WSL2 |
| Model | Anthropic's | Anthropic's, or third-party on the CLI, VS Code, and JetBrains | Hosted or local, your pick |
| Entry cost | A paid Claude plan | A paid Claude plan or Console account | Free software, you pay for model access |
| Security owner | Anthropic | Anthropic | You |
Two of these three are the same product wearing different clothes. Anthropic's help centre says Cowork "uses the same agentic architecture that powers Claude Code, with no terminal required". Both sit inside a paid Claude plan. Cowork is the younger surface: web and mobile are open to Pro, Max and Team, and to Enterprise where an admin turns it on, cloud execution is still labelled beta, and the Chrome side panel is still rolling out to Pro. Cloud sessions start from what Claude already remembers from your chats, what comes up carries back into chat, and some features stay desktop-only.
OpenClaw is the only one you host
OpenClaw calls itself "an AI assistant that runs on your devices and meets you in the channels you already use", connected "through one Gateway, for a single operator or for a team whose members trust each other". It is MIT-licensed under a non-profit foundation, runs on macOS, Linux, Windows and WSL2, and works with hosted or local model providers. Claude Code ships under a proprietary all-rights-reserved licence, so that independence is the real trade.
The channels gap is narrowing
OpenClaw's headline was meeting you where you already talk: WhatsApp, Telegram, Slack, Discord, Google Chat, Signal and iMessage. Claude Code now has Channels, a research preview covering Telegram, Discord and iMessage, where events "only arrive while the session is open". Narrower reach, pointed at coding work, and not always-on. The gap is smaller, not gone.
Self-hosting moves the security bill to you
OpenClaw's own documentation is blunt about this, which I respect. Tools "run on the host for the main session unless you configure sandboxing", and OpenClaw "is not a hostile multi-tenant security boundary for mutually adversarial users sharing one agent or gateway". The secure baseline is loopback binding with token auth, and the guidance is to never expose the Gateway unauthenticated on 0.0.0.0. There is an openclaw security audit command because you need one.
How to pick
Pay for a Claude plan and the Cowork question answers itself by task: repository work in Claude Code, everything else in Cowork. Choose OpenClaw when owning the host and the model matters more than the setup cost, and read the safer-agent comparison and Hermes vs OpenClaw vs Claude Code first. Still picking a coding agent? Start with Codex vs Claude Code vs GitHub Copilot, or OpenCode vs Claude Code vs Codex. Founders still deciding whether to write the code at all should start with the vibe code or hire check.
References
- Claude Help Center. "Get started with Claude Cowork"
- GitHub. openclaw/openclaw README
- OpenClaw documentation. "Gateway security"
- Claude Code documentation. "Channels"
Top comments (0)