How to Start OpenClaw in Verbose Mode

Verbose mode is most useful when you already know what you are trying to reproduce. Use it to capture one clean failure, not to leave a noisy process running forever.

Quick answer

Run the gateway with --verbose, optionally add --ws-log compact, and keep openclaw logs --follow open while you reproduce the issue.

Command line steps

1. Launch the gateway in verbose mode

This gives you a higher-signal startup path than repeated blind restarts.

openclaw gateway --verbose --ws-log compact

2. Follow the log stream

Use the logs command to keep a readable record while you test the failing action.

openclaw logs --follow --local-time

3. Reproduce only one issue at a time

Avoid changing models, channels, and config in the same pass or the log trail becomes useless.

openclaw gateway status --require-rpc
openclaw models status --check

What to check if it still fails

• If verbose mode still does not show the root problem, reproduce the issue from a smaller test case such as one DM or one model switch.
• If the gateway is managed as a service, stop the service before you launch a manual foreground debug process.
• If the logs point to config damage, hand off to openclaw doctor --fix before you keep collecting noise.