CLI commands should terminate after completing or after returning an error.

### Expected behavior

**Expected behavior**

```txt
CLI commands should terminate after completing or after returning an error.

### Actual behavior

`openclaw.mjs version` remained alive after 3 seconds and 13 seconds.

Observed process:

PID 22300 node.exe ... openclaw.mjs version

Observed memory:

After 3s: WorkingSet ~406MB
After 13s: WorkingSet ~459MB
Before cleanup: WorkingSet ~581MB

`openclaw.mjs status` also remained alive after 3 seconds and 13 seconds.

Observed process:

PID 26840 node.exe ... openclaw.mjs status

Observed memory:

After 3s: WorkingSet ~369MB
After 13s: WorkingSet ~454MB
Before cleanup: WorkingSet ~457MB

The gateway process was separate and remained healthy:

PID 20356 node.exe ... openclaw dist/index.js gateway --port 18789

Only the stuck CLI processes were manually stopped.

### OpenClaw version

OpenClaw 2026.4.26 

### Operating system

Windows11

### Install method

npm

### Model

cliproxyapi/Codex GPT5.5

### Provider / routing chain

OpenClaw -> CLIProxyAPI -> Codex GPT5.5

### Additional provider/model setup details

Health checks observed as OK:

```powershell
openclaw --version

### Logs, screenshots, and evidence

```shell