Name: OpenClaw CLI
Availability: InStock
Author: ramensushi2026

OpenClaw CLI

Run OpenClaw commands safely and efficiently. Choose the right command family, execute with the correct profile context, and verify postconditions.

Clarify the target state. Ask what should change and what must remain untouched.
Select runtime scope first. Use default profile unless isolation is requested. Use:

openclaw --profile <name> ...

for named isolated state under

~/.openclaw-<name>

Choose the command family. Use
```
references/command-map.md
```
to route the request quickly.
Expand command details before running risky operations. Run
```
openclaw <command> --help
```
for starred families and confirm flags.
Prefer machine-readable output when automation is needed. Use
```
--json
```
where available, then parse/verify.
Verify outcomes explicitly. Check with
```
openclaw status
```
,
```
openclaw health
```
,
```
openclaw nodes status --json
```
, or command-specific follow-up.

Require explicit user confirmation before
```
reset
```
,
```
uninstall
```
, destructive
```
--force
```
flows, or credential-clearing operations.
Prefer non-destructive diagnostics first:
```
status
```
,
```
health
```
,
```
doctor
```
,
```
logs
```
.
Keep profile usage consistent across a workflow. Do not mix default and
```
--dev
```
/
```
--profile
```
commands accidentally.
For gateway issues, diagnose before restart unless restart is explicitly requested.

For generic "OpenClaw not working" issues:

Check

openclaw gateway ...

openclaw node ...

, or

openclaw nodes ...

based on where failure appears.

```
references/command-map.md
```
: Command families, routing guidance, and practical recipes.