Checking Gateway Health with OpenClaw

I have spent too much time staring at a terminal, wondering if my local services are actually working or if they are just silently failing. It is a common frustration when you cannot tell if a connection issue is on your side or if the gateway itself has stopped responding.

I prefer having a direct way to verify that everything is running correctly. The openclaw health command is the best tool for this because it gives you an immediate status report without any guesswork.

What You’ll Need

• A running Gateway instance.
• OpenClaw CLI.

Quick Start

To see if your Gateway is active, run the basic health command:

openclaw health

If you are building a script or need to parse the data, use the JSON output:

openclaw health --json

I recommend using the verbose flag if you need to see exactly what is happening with your accounts. This runs live probes to check the status:

openclaw health --verbose

Troubleshooting

If you have multiple accounts configured, you might notice that some responses feel slower than others. You can identify which account is causing the delay by using the --verbose flag. It prints per-account timings so you can see the exact performance of each one.

When you have multiple agents running, the output also includes per-agent session stores. If an agent is not behaving as expected, check this output to ensure the sessions are being tracked properly.

For more help, talk to the AI Setup Assistant.

What’s Next

• Gateway Configuration
• Managing Agents