Problem

openclaw gateway status is the documented first-line operator check for runtime and RPC state, but its JSON output does not expose the running gateway version.

That makes post-update smoke tests harder than they need to be. After an update, the status surface can confirm that a gateway is running and reachable, but it cannot confirm which version is actually serving traffic.

This is especially useful for:

• post-update verification
• detecting CLI/service skew
• confirming a restarted daemon picked up the expected build
• MCP smoke tests that want a single structured status response

Evidence

Local docs position openclaw gateway status as the operator-facing runtime check:

• docs/help/troubleshooting.md
• docs/help/faq.md

Observed current JSON output from openclaw gateway status --json includes:

• service
• config
• gateway
• port
• rpc
• health
• extraServices

But it does not include a version string anywhere in the response.

Request

At minimum, something like this would solve the smoke-test gap:

{
  "service": "...",
  "gateway": {
    "version": "..."
  }
}

If there is already a distinction available internally, even better would be to include the runtime gateway version explicitly, and optionally CLI/service metadata separately.

Why this helps

A version field in status would make post-update verification much cleaner:

• one call can confirm the gateway is up
• one call can confirm the expected version is actually running
• automated smoke tests no longer need a second version-specific probe or log scrape