Complete reference for openclaw message, sending, reacting, polling, editing, broadcasting, and platform-specific actions across all configured channels. What does Openclaw Message do? It’s the CLI interface for all outbound and interactive message operations across every channel OpenClaw supports. A single command surface handles sending text or media, creating polls, reacting to messages...
Complete reference for openclaw memory, checking embedding and vector store health, triggering reindexes, and running semantic searches over your memory files. What does Openclaw Memory manage? OpenClaw’s memory system reads your MEMORY.md and memory/*.md files, embeds their contents via a configured provider, and stores the resulting vectors in a local...
Complete reference for openclaw logs, tailing live Gateway output, fetching snapshots, controlling output format, and streaming structured JSON for scripting. What does Openclaw Logs do? It connects to the running Gateway and streams its log output directly to your terminal, the same logs the Gateway is writing internally, delivered in real time. Without any flags, it fetches a recent snapshot...
Complete reference for openclaw hooks, discovering, enabling, installing, and managing hook packs, plus a reference for the four bundled hooks that ship with OpenClaw. What are Hooks? Hooks are event-driven extensions that run in response to Gateway activity, things like session starts, commands, or agent turns. They let you inject behavior without modifying the core Gateway: save context to...
Complete reference for openclaw health, fetching Gateway health snapshots, verbose provider probing, multi-agent session details, and targeting remote Gateways. What does Openclaw Health do? It queries the running Gateway over its local RPC connection and returns a health snapshot—a summary of whether the Gateway is up, which channels are connected, and (with –verbose) how those channels...