Skip to main content

​
openclaw triage

Run read-only Doctor checks, collect the existing sanitized diagnostics archive, and write a bounded Markdown prompt for an agent debugging this OpenClaw installation.
The prompt includes the OpenClaw version, platform, Node.js version, prioritized Doctor findings with repair hints, and the diagnostics archive path. The archive contains sanitized config, Gateway status and health snapshots, operational log summaries, and available stability diagnostics. If the Gateway is unreachable, triage still writes the prompt and explains why the archive is unavailable. Secrets, tokens, raw chat payloads, and raw logs are excluded. Paths inside the prompt are shown relative to ~ or $OPENCLAW_STATE_DIR; the saved prompt path, archive path, and printed handoff commands retain the real absolute paths needed by your shell. Doctor checks remain advisory and do not apply repairs.

​
Agent handoff

In an interactive terminal, triage detects the agent handoff routes available on the current machine and asks which one to use. A configured OpenClaw embedded agent appears first, followed by Claude Code when claude is on PATH, Codex CLI when codex is on PATH, and an option to just print the commands. Choosing Claude Code or Codex starts its interactive session directly with the generated prompt. Choosing the embedded agent first verifies the configured model with a live inference check, then runs one OpenClaw agent turn. --run requests that same verified embedded route explicitly. On Windows, agents installed only as .cmd or .bat command shims appear in the manual handoff commands instead of the direct-launch picker. Non-interactive sessions and the print-only choice provide these manual handoff commands instead:
JSON output also includes detectedAgents, listing the external agents found on PATH. JSON output and non-interactive sessions never start an agent.

​
Output and exit codes

The prompt is written to logs/support/ inside the state directory with owner-only permissions, alongside the diagnostics archive when one was produced. Both paths are printed, and --json returns them plus finding counts by severity. A launched agent inherits the current environment, so it inspects the same installation the prompt describes, including a custom OPENCLAW_STATE_DIR. Triage exits with the launched agent’s exit code. If the agent cannot be started, triage prints its manual command and exits non-zero. Selecting the embedded agent when no model is configured reports the missing model and exits non-zero without starting a turn.

​
Options

--json cannot be combined with --run. Related: Doctor, Gateway, and Troubleshooting.