Summary

openclaw --profile enterprise gateway status reports:

Service config issue: Service command does not include the gateway subcommand

even though the LaunchAgent command shown in the same output clearly includes gateway --port 18890.

Environment

• OS: macOS
• Install: npm global install
• CLI version: 2026.5.12-beta.5
• Running Gateway version: 2026.5.12-beta.4
• Service type: macOS LaunchAgent
• Profile: named profile (enterprise)

Repro

Run:

env -u OPENCLAW_GATEWAY_TOKEN openclaw --profile enterprise gateway status

Observed

The command output includes this LaunchAgent command:

Command: /bin/zsh -lc set -a; [ -f "$HOME/.config/api-keys.env" ] && . "$HOME/.config/api-keys.env"; set +a; unset OPENCLAW_GATEWAY_TOKEN; exec /opt/homebrew/opt/node/bin/node /Users/antonio/.npm-global/lib/node_modules/openclaw/dist/index.js gateway --port 18890

It also reports:

Service config looks out of date or non-standard.
Service config issue: Service command does not include the gateway subcommand

The same status output shows the gateway is otherwise reachable:

Connectivity probe: ok
Capability: admin-capable
Listening: 127.0.0.1:18890

Expected

The service audit should recognize shell-wrapped LaunchAgent commands that execute:

.../openclaw/dist/index.js gateway --port <port>

and should not report that the gateway subcommand is missing.

Impact

This creates misleading diagnostic noise during gateway recovery. In this case, the gateway was healthy and the shown command contained the gateway subcommand, but gateway status still suggested that the service command was malformed.

Notes

This may be specific to parsing /bin/zsh -lc "..." LaunchAgent wrappers. The command is intentionally shell-wrapped to load a global env file before starting the gateway.