Bug Description

After upgrading to 2026.4.12, long-running exec commands are frequently terminated with SIGKILL. The issue is not triggered on every conversation turn — it occurs after executing a task that takes longer than usual (e.g., compound exec commands, multi-step operations, or running the openclaw CLI).

Actual System Messages

After a long-running task completes, subsequent exec commands fail with SIGKILL and these system messages appear repeatedly:

System (untrusted): [2026-04-14 12:56:32 GMT+8] Exec failed (oceanic-, signal SIGKILL) System (untrusted): [2026-04-14 12:56:51 GMT+8] Exec failed (brisk-sl, signal SIGKILL) :: error: too many arguments for 'sessions'. Expected 0 arguments but got 1. System (untrusted): [2026-04-14 12:57:10 GMT+8] Exec failed (marine-c, signal SIGKILL) System (untrusted): [2026-04-14 12:57:29 GMT+8] Exec failed (good-mea, signal SIGKILL)

Note on the second entry: the command attempted was openclaw sessions list which returns an error oo many arguments for 'sessions'. Expected 0 arguments but got 1. — indicating that in 2026.4.12, the sessions subcommand no longer accepts list as a valid argument. This appears to be a CLI breaking change as well.

These system error messages appear in the conversation and are noisy. However, final output is still delivered correctly despite SIGKILL.

Expected Behavior

• Exec commands should complete or timeout gracefully without SIGKILL
• No system error messages should appear for normal command execution
• The sessions CLI command should work as expected (list subcommand should be valid)

Steps to Reproduce

1. Execute a compound or long-running exec command
2. After that task completes, try running another exec command (e.g., openclaw status, openclaw sessions list)
3. The subsequent command gets SIGKilled before completion
4. System error messages appear in the conversation

Environment

• Version: 2026.4.12 (1c0672b)
• OS: Windows 11 x64
• Node: v24.14.0
• Shell: PowerShell

Additional Context

• Final output is still delivered correctly despite SIGKILL (not a silent failure)
• The issue is consistent on Windows platform after long tasks
• The error messages clutter the conversation but do not affect functionality
• There also appears to be a breaking CLI change in the sessions subcommand (no longer accepts list)