Discover commands without copying a command dump

Verifiedon 2026-07-302026.7.1-2

Start with the executable you actually have

Run openclaw --version, then use openclaw --help and narrow help such as openclaw config --help, openclaw channels --help, and openclaw update --help. Help describes the installed command surface; documentation explains intent and constraints. Keep both in the record because command names and flags can change between releases.

Lab: make a five-row crib sheet

Capture only these columns: command, question answered, read/write classification, version, and safe follow-up. Start with --version, config validate, doctor, health, and channels status. Do not run a command merely because it appears in help. Mark config set, channels add/remove, update, and any --fix action as state-changing or potentially state-changing.

Decision check

A colleague sends openclaw update --yes in chat. Is help evidence enough to run it? No. First establish install method, update status, service ownership, maintenance window, rollback evidence, and whether the command will restart the gateway.

Evidence standard

A useful excerpt shows the version and the exact help scope, but never credentials, private paths, or copied terminal history. The next lesson uses this record to separate safe config reads from writes.