Bug
openclaw CLI commands (e.g. openclaw gateway status --json, openclaw browser status) sometimes hang and do not return to the shell prompt. This appears to be new/regression after recent update (2026.2.6-3). The CLI prints plugin init logs and stays running even for status/health commands.
Expected
Status/health commands should exit after printing JSON.
Actual
Process stays running; requires manual kill (Ctrl+C doesn’t always exit). timeout sometimes also does not terminate.
Steps to reproduce
openclaw gateway status --json
# or
openclaw browser status --browser-profile openclaw-managed --json
Output (trimmed)
[plugins] [unbrowse] Auto-discover: 3 existing skills loaded
[plugins] [token-refresh] Scheduler started (checking every 1min)
[plugins] [unbrowse] Auto-discovery hook active
[plugins] [unbrowse] Plugin registered (16 tools, auto-discover)
{ ... JSON status ... }
# hangs here
Environment
- OpenClaw: 2026.2.6-3
- OS: Linux (server)
- Gateway: systemd service, loopback
Notes
Seems like CLI is starting full runtime/plugins and not exiting for status commands. Possibly a regression in CLI lifecycle or plugin init.
Bug
openclawCLI commands (e.g.openclaw gateway status --json,openclaw browser status) sometimes hang and do not return to the shell prompt. This appears to be new/regression after recent update (2026.2.6-3). The CLI prints plugin init logs and stays running even for status/health commands.Expected
Status/health commands should exit after printing JSON.
Actual
Process stays running; requires manual kill (
Ctrl+Cdoesn’t always exit).timeoutsometimes also does not terminate.Steps to reproduce
openclaw gateway status --json # or openclaw browser status --browser-profile openclaw-managed --jsonOutput (trimmed)
Environment
Notes
Seems like CLI is starting full runtime/plugins and not exiting for status commands. Possibly a regression in CLI lifecycle or plugin init.