openclaw - 💡(How to fix) Fix [Bug]: `openclaw security audit` (and `--deep`) hangs silently on macOS 15.7.3 / 2026.4.29 [1 comments, 2 participants]

Either complete and print findings, or fail with a clear error within a reasonable time.

TL;DR

The issue can be mitigated by investigating and potentially downgrading or patching the Node version, as the problem seems to persist despite the inclusion of supposed fixes in OpenClaw version 2026.4.29.

Guidance

• Verify that the issue is not specific to the openclaw security audit command by testing other audit commands or tools that might be affected by the same underlying cause.
• Consider capturing a spindump or sample output of the hung node process for further analysis, as offered in the issue notes.
• Review the changes and fixes implemented in the recently closed issues (#75456, #75508) to understand if there might be a regression or if the fix did not fully address the problem.
• Investigate if there are known issues with Node version v24.15.0 that could be contributing to the hang, especially considering the Apple Silicon architecture.

Example

No specific code snippet can be provided without more details on the internal workings of OpenClaw or the exact nature of the hang. However, debugging the Node process or running OpenClaw with additional logging might yield useful insights.

Notes

The persistence of the issue despite the inclusion of fixes from #75456 and #75508 suggests that either the problem is more complex or the fixes did not fully address the root cause. The fact that all other openclaw subcommands work fine indicates the issue might be specific to the audit functionality.

Recommendation

Apply workaround: Given the complexity and the fact that the issue seems to involve a combination of OpenClaw, Node, and potentially macOS specifics, a straightforward upgrade to a fixed version is not clearly available. Thus, applying workarounds such as debugging the process, capturing more logs, or potentially adjusting the environment (e.g., Node version) seems to be the most viable next step.