Feature and support matrix

A high-level inventory of selected ZeroClaw capability sets, compared against OpenClaw and Hermes. It provides a quick starting point; feature-gated, non-default, and runtime-only capabilities may require the linked subsystem documentation.

The generated ZeroClaw sections below each reflect a specific source: the curated ChannelsConfig::channels() metadata list, canonical provider slots, or the minimal default tool set. They stay aligned with those inputs, but they are not exhaustive inventories of every compile-time channel or conditionally registered tool. The OpenClaw and Hermes columns come from docs/book/feature-matrix-parity.toml, the reviewable source for parity facts the binary has no knowledge of.

Status legend

Status	Icon	Meaning
Supported	✅	Implemented and documented; safe to rely on
Partial	🟡	Works with caveats or covers a subset of the surface
Experimental	🧪	Present but may change; validate before depending on it
Planned	📋	Tracked but not yet implemented
None	❌	Not available on that runtime
Unknown	❓	Support not established: not yet assessed or the available evidence is inconclusive

Runtime and deployment modes

Mode	Status	Reference
Local CLI (`zeroclaw agent`)	✅	Quickstart
Daemon / OS service	✅	Service
Gateway HTTP + web dashboard	✅	Gateway HTTP API, Web dashboard
ZeroCode terminal UI	✅	ZeroCode
Container	✅	Container
Linux / macOS / Windows	✅	Linux, macOS, Windows
FreeBSD / NixOS	✅	FreeBSD, NixOS
SBC / edge (Raspberry Pi class)	✅	Hardware
VPS / cloud VM	✅	Network deployment

Curated channel metadata support

Generated from the manually curated ChannelsConfig::channels() metadata list. Compile-only or non-config channel surfaces may be outside this table. The canonical per-channel setup detail lives on each channel’s own page.

Channel	ZeroClaw	OpenClaw	Hermes
Telegram	✅	✅	✅
Discord	✅	✅	✅
Slack	✅	✅	✅
Mattermost	✅	✅	✅
iMessage	✅	✅	✅
Matrix	✅	✅	✅
Signal	✅	✅	✅
WhatsApp	✅	✅	✅
WhatsApp Web	✅	✅	✅
Linq	✅	❌	❌
NextCloud Talk	✅	✅	❌
Email	✅	❌	✅
Gmail Push	✅	❌	❌
Twitch	✅	✅	❌
IRC	✅	✅	✅
Lark	✅	✅	✅
DingTalk	✅	❌	✅
WeCom	✅	❌	✅
WeCom WebSocket	✅	❌	✅
WeChat	✅	❌	✅
QQ Official	✅	✅	✅
Nostr	✅	✅	❌
ClawdTalk	✅	❌	❌
Reddit	✅	❌	❌
Bluesky	✅	❌	❌
Git	✅	❓	❓
X/Twitter	✅	❌	❌
Mochat	✅	❌	❌
LINE	✅	✅	✅
Voice Call	✅	✅	❌
VoiceWake	✅	❌	❌
MQTT	✅	❌	❌
AMQP	✅	❌	❌
Filesystem	✅	❌	❌
Webhook	✅	✅	✅
Plugin	✅	❓	❓

Provider slot support

Generated from the canonical model-provider slots (canonical_model_provider_slots). See the Providers overview for per-provider configuration.

Provider slot	ZeroClaw	OpenClaw	Hermes
`openai`	✅	✅	✅
`azure`	✅	✅	✅
`anthropic`	✅	✅	✅
`moonshot`	✅	✅	✅
`qwen`	✅	✅	✅
`glm`	✅	✅	✅
`minimax`	✅	✅	✅
`zai`	✅	✅	✅
`doubao`	✅	✅	❓
`yi`	✅	❌	❌
`hunyuan`	✅	❌	❌
`qianfan`	✅	✅	❌
`baichuan`	✅	❌	❌
`openrouter`	✅	✅	✅
`ollama`	✅	✅	🟡
`hailo_ollama`	✅	❓	❓
`gemini`	✅	✅	✅
`gemini_cli`	✅	✅	❌
`grok_cli`	✅	❌	❌
`bedrock`	✅	✅	✅
`telnyx`	✅	❌	❌
`together`	✅	✅	✅
`fireworks`	✅	✅	✅
`groq`	✅	✅	✅
`mistral`	✅	✅	✅
`deepseek`	✅	✅	✅
`atomic_chat`	✅	❌	❌
`cohere`	✅	✅	✅
`perplexity`	✅	❌	✅
`xai`	✅	✅	✅
`cerebras`	✅	✅	✅
`crusoe`	✅	❓	❓
`sambanova`	✅	❌	❌
`hyperbolic`	✅	❌	❌
`deepinfra`	✅	✅	✅
`huggingface`	✅	✅	✅
`ai21`	✅	❌	❌
`reka`	✅	❌	❌
`baseten`	✅	❌	❌
`nscale`	✅	❌	❌
`anyscale`	✅	❌	❌
`nebius`	✅	❌	❌
`friendli`	✅	❌	❌
`stepfun`	✅	✅	✅
`aihubmix`	✅	❌	❌
`siliconflow`	✅	❌	❌
`astrai`	✅	❌	❌
`avian`	✅	❌	❌
`deepmyst`	✅	❌	❌
`venice`	✅	✅	❓
`nearai`	✅	❌	❌
`novita`	✅	✅	✅
`nvidia`	✅	✅	✅
`vercel`	✅	✅	❌
`cloudflare`	✅	✅	❓
`atlascloud`	✅	❓	❓
`ovh`	✅	❌	❌
`copilot`	✅	✅	✅
`lmstudio`	✅	✅	✅
`llamacpp`	✅	✅	🟡
`sglang`	✅	✅	🟡
`vllm`	✅	✅	🟡
`osaurus`	✅	❌	❌
`litellm`	✅	✅	🟡
`lepton`	✅	❌	❌
`manifest`	✅	❌	❌
`morph`	✅	❌	❌
`github_models`	✅	❌	❌
`upstage`	✅	❌	❌
`featherless`	✅	❌	❌
`arcee`	✅	✅	✅
`lambda_ai`	✅	❌	❌
`inception`	✅	❌	❌
`synthetic`	✅	✅	❌
`opencode`	✅	✅	❌
`kilocli`	✅	✅	❌
`kilo`	✅	✅	❌
`zerorouter`	✅	❓	❓
`custom`	✅	✅	✅

Default tool support

Generated from the minimal default tool registry (default_tools). Conditional and full-runtime tools are outside this table; their canonical inventory and gating rules live in the Tools overview and built-in tool inventory.

Tool	ZeroClaw	OpenClaw	Hermes
`shell`	✅	✅	✅
`file_read`	✅	✅	✅
`deliver_file`	✅	❓	❓
`file_write`	✅	✅	✅
`file_edit`	✅	✅	✅
`glob_search`	✅	✅	✅
`content_search`	✅	✅	✅

SOP support

Standard Operating Procedures are deterministic, trigger-matched procedures run by the SopEngine with approval gates and auditable run state (how they run, syntax). This row is hand-recorded rather than code-walked: SOP is not part of the channel, provider, or tool registries the tables above are generated from.

Capability	ZeroClaw	OpenClaw	Hermes
Deterministic SOP engine (trigger match, approval gates, audited runs)	🧪	❌	🟡

ZeroClaw’s SopEngine is present but still maturing: authenticated webhooks, MQTT, filesystem, AMQP, and the daemon’s cron maintenance tick are wired live fan-in sources, while peripheral and calendar triggers are defined and matched but not yet routed to a live source, so the capability is experimental. OpenClaw has no deterministic-procedure engine (its exec-approval flow is a per-tool permission prompt, not a step runner), so it is none. Hermes ships cron and webhook “routines” that pair a trigger with a free-form agent prompt but no deterministic multi-step engine, approval gates, or audited run state, so it is partial on the trigger side only.

ZeroClaw, OpenClaw, and Hermes

ZeroClaw is a from-scratch runtime, not a fork. The comparison columns state factual support status per runtime; they are not a marketing scorecard. Where a concept maps onto OpenClaw or Hermes, the migration and parity notes live with the relevant feature page rather than in a standalone comparison.

Integration prerequisites

Some capabilities require external infrastructure. Where a channel or tool needs a gateway, public webhook, tunnel, cloud account, local model, or plugin, that requirement is stated on the linked page. Consult the specific channel, provider, or tool reference before assuming a setup works without one.

Keyboard shortcuts

ZeroClaw Docs