Skip to content
RemoteClaw

Coming from OpenClaw

Coming from OpenClaw

RemoteClaw is a fork of OpenClaw that replaced the embedded AI execution engine with a middleware architecture. If you’re coming from OpenClaw, here’s what changes and what stays the same.

What stays

RemoteClaw inherits OpenClaw’s channel infrastructure. The 20+ messaging adapters (WhatsApp, Telegram, Discord, Slack, iMessage, and more), the gateway, the plugin system, and the native apps all carry over. Your channel configurations import directly.

What changes

RemoteClaw gutted OpenClaw’s embedded execution engine and replaced it with a CLI subprocess bridge. Instead of running an LLM inside its own process, RemoteClaw launches your existing CLI agent (Claude Code, Gemini CLI, Codex CLI, or OpenCode) as a subprocess.

This means:

  • Your agent config is preserved. Your ~/.claude, ~/.gemini, or other agent setup works as-is — no reconfiguration inside RemoteClaw.
  • No built-in model catalog. OpenClaw ships many LLM providers with a picker wizard. RemoteClaw delegates model selection entirely to your CLI agent.
  • No skills marketplace. ClawHub and the skills system are removed. Agents bring their own capabilities via MCP or built-in tools.
  • No Docker sandbox. Agents manage their own sandboxing. RemoteClaw provides process isolation via the subprocess boundary.
  • No provider auth management. Agents use their own API keys or subscriptions via environment variables.

Architecture side by side

RemoteClaw (middleware)
├── ChannelBridge (message routing + session tracking)
├── CLI subprocess (claude, gemini, codex, or opencode)
│   ├── LLM interaction (handled by the CLI)
│   ├── Tool execution (handled by the CLI)
│   └── Conversation management (handled by the CLI)
└── MCP server (injected into subprocess for gateway access)

The CLI agent owns the agentic loop. RemoteClaw handles session persistence, message delivery, and MCP tool bridging.

For a deeper architectural comparison, see Middleware Architecture — How This Differs from OpenClaw.

Ready to switch?

See Migrate from OpenClaw for step-by-step instructions and Breaking changes for the full list of what’s removed and what’s new.

If RemoteClaw isn’t the right fit, OpenClaw remains a great choice for anyone who wants a self-contained platform with built-in model providers and a skills marketplace.