1. 其他工具 - 任何在参数验证时直接抛出普通 Error 的工具都可能触发相同问题
2. Trigger a tool parameter validation error (e.g., call read with empty path or web_fetch with invalid URL)
3. Observe the error is not marked as retryable: false
4. Check logs for repeated error messages (hundreds of times) Parameter validation errors should be marked as non-retryable (retryable: false) and stop immediately without looping. The error should be returned to the user once. The tool parameter validation error triggers an infinite retry loop, causing 200+ duplicate messages and wasting API tokens. The error is treated as retryable and keeps retrying indefinitely.

TL;DR

Mark parameter validation errors as non-retryable (retryable: false) to prevent infinite retry loops in the OpenClaw framework.

Guidance

• Identify the source of parameter validation errors in tools like read and web_fetch to ensure they are correctly marked as non-retryable.
• Review the error handling mechanism in the OpenClaw framework to prevent it from treating parameter validation errors as retryable.
• Implement a check to stop retrying when a parameter validation error occurs, and return the error to the user immediately.
• Consider adding logging to track the number of retries and detect potential infinite loops.

Example

// Example of marking a parameter validation error as non-retryable
const error = new Error('Missing required parameter: path');
error.retryable = false;
throw error;

Notes

The solution may require modifications to the OpenClaw framework and individual tools to correctly handle parameter validation errors. The provided example is a simplified illustration and may need to be adapted to the actual codebase.

Recommendation

Apply workaround: Modify the error handling mechanism to mark parameter validation errors as non-retryable (retryable: false) to prevent infinite loops, as the root cause seems to be related to how these errors are handled rather than a version-specific issue.