TL;DR

Investigate the exec tool configuration or implementation to identify why it is sending a SIGKILL signal to OpenClaw CLI subcommands after they produce output.

Guidance

• Verify if the issue persists when running OpenClaw CLI subcommands directly without the exec tool to isolate the problem.
• Check the exec tool's documentation or source code to see if there are any settings or options that could be causing it to send a SIGKILL signal after command execution.
• Compare the behavior of the exec tool with other command execution methods to determine if this is a specific issue with the exec tool or a more general problem.
• Test if the issue is specific to the OpenClaw version 2026.4.8 or if it also occurs with previous versions.

Example

No specific code example is provided as the issue seems to be related to the interaction between the exec tool and OpenClaw CLI, and without more information about the exec tool's implementation, it's difficult to provide a relevant code snippet.

Notes

The fact that Gateway API calls work normally suggests that the issue is specific to the CLI or the exec tool, rather than a general problem with OpenClaw.

Recommendation

Apply workaround: Investigate alternative command execution methods or tools that do not send a SIGKILL signal after command execution, as the root cause of the issue seems to be related to the exec tool's behavior.