Summary

In OpenClaw 2026.5.6, gateway run --port 18789 accepts --port, but adjacent gateway subcommands reject the same flag:

• openclaw gateway health --port 18789 -> error: unknown option '--port'
• openclaw gateway probe --port 18789 -> error: unknown option '--port'

This makes scripts awkward because run can target a non-default port but health/probe cannot target the same port through the same visible option shape.

Environment

• OpenClaw: 2026.5.6 (c97b9f7)
• Node: v24.15.0
• OS: Windows
• Install: isolated npm install of openclaw@latest
• Profile: imladri-sidequest
• Gateway: loopback, port 18789

Reproduction

openclaw --profile imladri-sidequest gateway run --dev --port 18789 --auth none --bind loopback --force --allow-unconfigured
openclaw --profile imladri-sidequest gateway health --port 18789
openclaw --profile imladri-sidequest gateway probe --port 18789

Actual

Both subcommands reject --port:

error: unknown option '--port'

Expected

Either:

1. gateway health and gateway probe should accept --port like gateway run, or
2. the help output should clearly document the supported way to target a non-default local gateway for health/probe checks.

Why this matters

Local automation and integration tests often start OpenClaw on a controlled port. It is natural to expect adjacent gateway commands to accept the same targeting option.