OpenClaw Field Guide · 21 of 24

20 · Terminal basics

Updated 24 September 2026 · Community edition

A terminal runs commands on the machine where it is open. A chat message containing a command does not necessarily execute it. Check which host and folder you are using.

Read-only starting points

openclaw --version
openclaw --help
openclaw status
openclaw gateway status

On macOS/Linux shells, pwd shows the current directory, ls lists it, and cd changes directories. Windows shells have their own path and command conventions.

Learn a command before using it

openclaw config --help
openclaw skills --help
openclaw update --help

Help is useful when your installed version differs from a guide. Run lines separately. A line beginning with # in a shell example is a comment, not the next command.

Know which commands change state

configure, update, install commands, and Gateway start/stop/restart alter the system. doctor --fix is not the same as inspecting doctor findings. Review effects before using mutation flags.

Share diagnostics carefully

Inspect logs locally and redact credentials, private URLs, and personal content before sharing excerpts. Do not publish the whole configuration or state directory to explain one error. Stopping a log-follow command with Ctrl+C ends that viewer, not necessarily the Gateway.