chore: apply event sweep result for openclaw-openclaw#74378

Author: github-actions[bot]

records/openclaw-openclaw/items/74378.md

@@ -0,0 +1,188 @@
+---
+review_comment_synced_at: 2026-04-29T14:05:47.137Z
+number: 74378
+repository: openclaw/openclaw
+type: issue
+title: "[Bug]: OpenClaw CLI commands remain alive as node.exe processes after execution on Windows"
+url: https://github.com/openclaw/openclaw/issues/74378
+state_at_review: open
+item_created_at: 2026-04-29T14:00:18Z
+item_updated_at: 2026-04-29T14:00:36Z
+author: 2ndNuts
+author_association: NONE
+labels: ["bug","regression"]
+reviewed_at: 2026-04-29T14:04:41.274Z
+main_sha: 0544c6d493ff89887b3480aaf9fa7e326d9357fc
+pull_head_sha: unknown
+latest_release: v2026.4.26
+latest_release_sha: be8c24633aaa7ef0425ae1178f096ee8dd6226c0
+fixed_release: unknown
+fixed_sha: unknown
+fixed_at: unknown
+review_policy: bdf05b6f0cc69e54
+review_model: gpt-5.5
+review_reasoning_effort: high
+review_sandbox: danger-full-access
+review_service_tier: fast
+review_mode: propose
+review_status: complete
+local_checkout_access: verified
+item_snapshot_hash: cfbcb52336c7364105ca967c7a4cc18dfa591d1cacf05f459581582e63f5c8ed
+close_comment_sha256: none
+review_comment_sha256: aa6db1288582d1f726552db7f15d6662f4022bbe390eb1ddf1d8e0ce895973b1
+review_comment_id: 4344473502
+review_comment_url: https://github.com/openclaw/openclaw/issues/74378#issuecomment-4344473502
+decision: keep_open
+close_reason: none
+confidence: high
+action_taken: kept_open
+work_candidate: queue_fix_pr
+work_confidence: medium
+work_priority: high
+work_status: candidate
+work_reason_sha256: dabe84245b8106dc04d3fa298cb8fab8bfa5178ced181861cc65d5b133d2f24f
+work_prompt_sha256: db960cd1c582ab013ec6d03f329b00d4efa7ea469f3725ba04ab624015ec088d
+work_cluster_refs: ["openclaw/openclaw#74378"]
+work_validation: ["pnpm test src/cli/run-main.exit.test.ts src/infra/net/undici-global-dispatcher.test.ts src/cli/program/routes.test.ts","pnpm exec oxfmt --check --threads=1 src/cli/run-main.ts src/infra/net/undici-global-dispatcher.ts src/cli/run-main.exit.test.ts src/infra/net/undici-global-dispatcher.test.ts","Windows npm smoke: run `node <npm-global-openclaw>/openclaw.mjs status` and `node <npm-global-openclaw>/openclaw.mjs --version`; both should exit within a few seconds and leave no `node.exe ... openclaw.mjs <command>` process.","pnpm check:changed"]
+work_likely_files: ["src/cli/run-main.ts","src/infra/net/undici-global-dispatcher.ts","src/cli/run-main.exit.test.ts","src/infra/net/undici-global-dispatcher.test.ts","src/entry.version-fast-path.ts","CHANGELOG.md"]
+---
+
+# [#74378: [Bug]: OpenClaw CLI commands remain alive as node.exe processes after execution on Windows](https://github.com/openclaw/openclaw/issues/74378)
+
+Type: issue
+
+URL: [https://github.com/openclaw/openclaw/issues/74378](https://github.com/openclaw/openclaw/issues/74378)
+
+Author: 2ndNuts
+
+Author association: NONE
+
+Labels: bug, regression
+
+Created at: Apr 29, 2026, 14:00 UTC
+
+Updated at: Apr 29, 2026, 14:00 UTC
+
+Reviewed against: [0544c6d493ff](https://github.com/openclaw/openclaw/commit/0544c6d493ff89887b3480aaf9fa7e326d9357fc)
+
+Codex review: model gpt-5.5, reasoning high
+
+Latest release at review time: [v2026.4.26](https://github.com/openclaw/openclaw/releases/tag/v2026.4.26) ([be8c24633aaa](https://github.com/openclaw/openclaw/commit/be8c24633aaa7ef0425ae1178f096ee8dd6226c0))
+
+Fixed in: not determined
+
+## Decision
+
+Keep open: kept open
+
+Confidence: high
+
+Action taken: kept_open
+
+## Summary
+
+Keep open. Current main still lacks an evident fix for the Windows process-lifetime regression: `status` is routed as a short-lived read-only CLI command, but the route path still bootstraps process-wide proxy/Undici state and then returns without a general active-handle teardown. The documented `--version` fast path exits directly, but the documented `status` reproduction is enough to keep this actionable.
+
+## What This Changes
+
+The report asks for Windows npm-installed OpenClaw CLI commands such as `version` and `status` to terminate after completing instead of leaving `node.exe openclaw.mjs <command>` processes alive.
+
+## Best Possible Solution
+
+Add a focused CLI lifecycle fix so short-lived non-daemon commands clean up process-wide proxy/Undici/debug-capture resources and exit naturally on Windows, while preserving long-running gateway/agent behavior and existing proxy routing semantics.
+
+## Work Candidate
+
+Candidate: queue_fix_pr
+
+Confidence: medium
+
+Priority: high
+
+Status: candidate
+
+Reason: This is a fresh regression with a narrow CLI lifecycle surface and clear likely files, but the repair should first identify the Windows active handle and avoid changing proxy/security semantics beyond teardown for short-lived commands.
+
+Cluster refs:
+
+- openclaw/openclaw#74378
+
+Likely files:
+
+- src/cli/run-main.ts
+- src/infra/net/undici-global-dispatcher.ts
+- src/cli/run-main.exit.test.ts
+- src/infra/net/undici-global-dispatcher.test.ts
+- src/entry.version-fast-path.ts
+- CHANGELOG.md
+
+Validation:
+
+- pnpm test src/cli/run-main.exit.test.ts src/infra/net/undici-global-dispatcher.test.ts src/cli/program/routes.test.ts
+- pnpm exec oxfmt --check --threads=1 src/cli/run-main.ts src/infra/net/undici-global-dispatcher.ts src/cli/run-main.exit.test.ts src/infra/net/undici-global-dispatcher.test.ts
+- Windows npm smoke: run `node <npm-global-openclaw>/openclaw.mjs status` and `node <npm-global-openclaw>/openclaw.mjs --version`; both should exit within a few seconds and leave no `node.exe ... openclaw.mjs <command>` process.
+- pnpm check:changed
+
+## Repair Work Prompt
+
+Fix openclaw/openclaw#74378. Investigate why short-lived Windows npm CLI invocations such as `node .../openclaw.mjs status` remain alive after output. Focus on CLI lifecycle cleanup for routed/non-daemon commands: `src/cli/run-main.ts`, env proxy/bootstrap handling, and `src/infra/net/undici-global-dispatcher.ts`. Preserve existing proxy routing semantics and long-running commands (`gateway`, `node run`, live provider/plugin commands); do not paper over the bug by forcing `process.exit` for every successful command unless tests prove it is the least risky boundary. Add focused regression coverage for routed `status` with env proxy/global dispatcher cleanup, and cover the version/unknown-command distinction as appropriate. Add a changelog fix entry if runtime behavior changes, crediting `Thanks @2ndNuts`. Do not change dependency versions or bundled plugin behavior.
+
+## Evidence
+
+- **Fresh user report:** The issue reports OpenClaw 2026.4.26 on Windows 11 via npm leaving `node.exe ... openclaw.mjs version` and `node.exe ... openclaw.mjs status` alive after 3 and 13 seconds, while the gateway process remained separate and healthy.
+- **Status is a routed short-lived CLI command:** Current main maps `status` to a routed command with plugins disabled and network proxy bypass, so it should complete without becoming a long-running runtime process.
+  - file: [src/cli/command-catalog.ts:94](https://github.com/openclaw/openclaw/blob/0544c6d493ff89887b3480aaf9fa7e326d9357fc/src/cli/command-catalog.ts#L94)
+  - command: `nl -ba src/cli/command-catalog.ts | sed -n '1,260p'`
+  - sha: [0544c6d493ff](https://github.com/openclaw/openclaw/commit/0544c6d493ff89887b3480aaf9fa7e326d9357fc)
+- **Routed status executes and returns:** The routed status definition loads `statusCommand` or `statusJsonCommand`, awaits it, and returns; there is no command-specific process termination or active-handle cleanup here.
+  - file: [src/cli/program/routed-command-definitions.ts:68](https://github.com/openclaw/openclaw/blob/0544c6d493ff89887b3480aaf9fa7e326d9357fc/src/cli/program/routed-command-definitions.ts#L68)
+  - command: `nl -ba src/cli/program/routed-command-definitions.ts | sed -n '1,320p'`
+  - sha: [0544c6d493ff](https://github.com/openclaw/openclaw/commit/0544c6d493ff89887b3480aaf9fa7e326d9357fc)
+- **CLI route path still bootstraps env proxy dispatcher:** Before routed commands, `runCli` calls proxy capture/bootstrap, which can install a global Undici env proxy dispatcher when proxy environment variables are present.
+  - file: [src/cli/run-main.ts:239](https://github.com/openclaw/openclaw/blob/0544c6d493ff89887b3480aaf9fa7e326d9357fc/src/cli/run-main.ts#L239)
+  - command: `nl -ba src/cli/run-main.ts | sed -n '260,640p'`
+  - sha: [0544c6d493ff](https://github.com/openclaw/openclaw/commit/0544c6d493ff89887b3480aaf9fa7e326d9357fc)
+- **No general dispatcher teardown after routed commands:** The `finally` block removes managed-proxy signal handlers, stops the managed proxy if one was started, and closes memory managers, but it does not restore or close an env-installed global Undici dispatcher for short-lived route commands.
+  - file: [src/cli/run-main.ts:603](https://github.com/openclaw/openclaw/blob/0544c6d493ff89887b3480aaf9fa7e326d9357fc/src/cli/run-main.ts#L603)
+  - command: `nl -ba src/cli/run-main.ts | sed -n '260,640p'`
+  - sha: [0544c6d493ff](https://github.com/openclaw/openclaw/commit/0544c6d493ff89887b3480aaf9fa7e326d9357fc)
+- **Global Undici dispatcher is replaced but not closed:** `ensureGlobalUndiciEnvProxyDispatcher` sets a new `EnvHttpProxyAgent` as the process global dispatcher; the helper tracks applied state but has no close/destroy/reset hook for command teardown.
+  - file: [src/infra/net/undici-global-dispatcher.ts:91](https://github.com/openclaw/openclaw/blob/0544c6d493ff89887b3480aaf9fa7e326d9357fc/src/infra/net/undici-global-dispatcher.ts#L91)
+  - command: `nl -ba src/infra/net/undici-global-dispatcher.ts | sed -n '1,240p'`
+  - sha: [0544c6d493ff](https://github.com/openclaw/openclaw/commit/0544c6d493ff89887b3480aaf9fa7e326d9357fc)
+- **Existing test asserts no forced exit for routed commands:** The current regression test suite explicitly verifies that a successful routed `status` command does not call `process.exit`, so current coverage would not catch a Windows active-handle leak that prevents natural process exit.
+  - file: [src/cli/run-main.exit.test.ts:225](https://github.com/openclaw/openclaw/blob/0544c6d493ff89887b3480aaf9fa7e326d9357fc/src/cli/run-main.exit.test.ts#L225)
+  - command: `nl -ba src/cli/run-main.exit.test.ts | sed -n '225,239p'`
+  - sha: [0544c6d493ff](https://github.com/openclaw/openclaw/commit/0544c6d493ff89887b3480aaf9fa7e326d9357fc)
+- **Relevant local related reports are not canonical duplicates:** The provided title-search overlaps cover Feishu command routing and older Anthropic initialization failures; none tracks this Windows `node.exe` process-lifetime leak.
+
+## Likely Related People
+
+- **masatohoshino:** introduced current CLI route/proxy lifecycle surface
+  - reason: Blame on `src/cli/run-main.ts`, `src/infra/net/undici-global-dispatcher.ts`, `src/cli/command-catalog.ts`, and `src/cli/program/routed-command-definitions.ts` points to commit `016f5ae8`, which introduced the current routed CLI/proxy dispatcher code paths involved in this report.
+  - confidence: high
+  - commits: 016f5ae862e1704b522808c6e79409da83425d63
+  - files: src/cli/run-main.ts, src/infra/net/undici-global-dispatcher.ts, src/cli/command-catalog.ts, src/cli/program/routed-command-definitions.ts
+- **steipete:** recent adjacent maintainer
+  - reason: Recent command-catalog policy maintenance touched the same CLI routing/proxy policy area, though not the central process-lifetime code.
+  - confidence: medium
+  - commits: 390a7598c952bda5db6a423e02db66c9db351f30
+  - files: src/cli/command-catalog.ts
+
+## Risks / Open Questions
+
+- Windows/npm reproduction was not performed in this read-only Linux review, so the exact active handle still needs confirmation on Windows.
+- The positional `version` command is not the documented version path; the fix should distinguish documented `openclaw --version` behavior from unknown-command handling while still addressing `status`.
+
+## Close Comment
+
+_No close comment posted._
+
+## GitHub Snapshot
+
+- comments: 0
+- timeline events: 2
+- related items: 5
+- PR files: 0
+- PR commits: 0
+