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...
Complete reference for openclaw gateway, running foreground processes, managing background services, diagnostics, network discovery, and low-level RPC invocation. What is the Gateway? The Gateway is the central process that connects OpenClaw’s CLI, agent runtimes, and external chat channels. Everything routes through it, incoming messages from WhatsApp, Slack, or Telegram; outgoing agent...
Complete reference for openclaw doctor, running health checks, applying config repairs, and auditing six categories of system state across config, services, auth, security, and more. What does Openclaw Doctor do? It’s OpenClaw’s all-in-one diagnostic and repair tool. A single run audits six distinct system areas, config schema, state integrity, model auth, background services...
