docs/cli/status.md
openclaw statusDiagnostics for channels + sessions.
openclaw status
openclaw status --all
openclaw status --deep
openclaw status --usage
Notes:
--deep runs live probes (WhatsApp Web + Telegram + Discord + Slack + Signal).openclaw status stays on the fast read-only path and marks memory as not checked instead of unavailable when it skips memory inspection. Heavy security audit, plugin compatibility, and memory-vector probes are left to openclaw status --all, openclaw status --deep, openclaw security audit, and openclaw memory status --deep.status --json --all reports memory details from the active memory plugin runtime selected by plugins.slots.memory. Custom memory plugins can leave built-in agents.defaults.memorySearch.enabled disabled and still report their own files, chunks, vector, and FTS state.--usage prints normalized provider usage windows as X% left.Execution: from Runtime:. Execution is the sandbox path (direct, docker/*), while Runtime tells you whether the session is using OpenClaw Pi Default, OpenAI Codex, a CLI backend, or an ACP backend such as codex (acp/acpx). See Agent runtimes for the provider/model/runtime distinction.usage_percent / usagePercent fields are remaining quota, so OpenClaw inverts them before display; count-based fields win when present. model_remains responses prefer the chat-model entry, derive the window label from timestamps when needed, and include the model name in the plan label./status can backfill token and cache counters from the most recent transcript usage log. Existing nonzero live values still win over transcript fallback values./status includes compact Gateway process uptime and host system uptime.0 token displays.openclaw update (see Updating).status, status --json, status --all) resolve supported SecretRefs for their targeted config paths when possible.secretDiagnostics.status --all includes a Secrets overview row and a diagnosis section that summarizes secret diagnostics (truncated for readability) without stopping report generation.