OpenClaw runs on your machine or an ephemeral sandbox. Each session starts fresh. Phantom gets its own dedicated VM that persists. The ClickHouse instance it built three weeks ago is still running and queryable.

OpenClaw spends a lot of tokens on screen understanding and vision loops. About 60% of its skills are basic macOS-level computer use (clicking, typing, reading the screen). Phantom skips that entirely and uses the Claude Agent SDK directly, so it gets full shell, file system, git, web search, and MCP tools natively without the token overhead of parsing screenshots.

The biggest difference is probably dynamic MCP. Phantom registers its own MCP tools at runtime, and they persist across restarts. It built a ClickHouse REST API, registered it as a tool, and now any Claude Code session or other agent that connects to it can query that data. It builds its own capabilities and exposes them as an API.

It also has persistent vector memory across sessions (Qdrant, local), a self-evolution engine where a different model validates every config change, and we built a companion tool called Specter (https://github.com/ghostwright/specter) that provisions VMs with DNS, TLS, and systemd in under 90 seconds, so deploying a new Phantom is genuinely three commands.

Both are good projects, different approaches. OpenClaw does computer use well. Phantom is a persistent co-worker that lives on its own machine and compounds over time.

That said, my initial reaction was the same and if the human wasn't involved and did not do its due diligence I'm right there with you