USE GUIDE — OPENCLAW

Main takeaway: check health first, then run tasks, then verify output

CLI means command-line interface, a text-based way to control OpenClaw quickly and consistently.

WINDOWS

PowerShell daily check

openclaw gateway status
openclaw help
openclaw gateway restart

Expected result: status returns healthy, help shows commands, restart completes in a few seconds.

macOS

Terminal daily check

openclaw gateway status
openclaw help
openclaw gateway restart

Expected result: same output pattern as Windows and gateway returns to healthy state.

Linux

Terminal daily check

openclaw gateway status
openclaw help
openclaw gateway restart

Expected result: no command errors and status reports the service as running.

WORKSPACE

Run from project folder

mkdir openclaw-demo
cd openclaw-demo
openclaw help

Expected result: OpenClaw commands work from a normal project directory.

PRACTICAL FLOW

3-minute operator routine

1) Confirm gateway status, 2) run one command from help that you use often, 3) log any errors with timestamp. This gives a fast baseline before bigger tasks.

Use case: before starting automation sessions, agent jobs, or guide walkthroughs.

TROUBLESHOOTING

Common fixes

If command is not found, open a fresh terminal and check PATH.

If gateway hangs, run openclaw gateway stop then openclaw gateway start.

If issues persist, revisit OpenClaw setup and confirm install version.

IF NEEDED

Install first

Run setup if your checks fail or if command paths are missing.

Open setup guide →