openclaw - 💡(How to fix) Fix Hardcoded 120s timeout in channel layer overrides configurable timeoutSeconds [1 participants]

const timeoutPromise = new Promise((_, reject) => setTimeout(() => reject(new Error("Agent response timeout (120s)")), 12e4)); Manually patch dist/channel-D5chgcOT.js changing 12e4 to the desired timeout in milliseconds (e.g. 6e5 for 600s) and updating the error message string.

TL;DR

Update the hardcoded timeout in dist/channel-D5chgcOT.js to respect the configured timeoutSeconds value from openclaw.json.

Guidance

• Identify the line of code overriding the agents.defaults.timeoutSeconds setting and consider modifying it to use the configured value instead of a hardcoded timeout.
• Verify the fix by setting agents.defaults.timeoutSeconds to a high value (e.g., 600) in openclaw.json and running a task that takes longer than the original hardcoded timeout (120 seconds).
• To mitigate the issue without modifying the compiled code, manually patch dist/channel-D5chgcOT.js as described in the provided workaround.
• Consider reaching out to the OpenClaw maintainers to report the issue and request a fix that respects the configured timeout value.

Example

const timeoutSeconds = agents.defaults.timeoutSeconds;
const timeoutPromise = new Promise((_, reject) => setTimeout(() => reject(new Error(`Agent response timeout (${timeoutSeconds}s)`)), timeoutSeconds * 1000));

Notes

The provided workaround requires manual modification of compiled code, which may not be ideal for production environments. A more permanent fix would involve updating the OpenClaw code to respect the configured timeout value.

Recommendation

Apply workaround: Manually patch dist/channel-D5chgcOT.js to use the desired timeout value, as this provides a temporary solution until a more permanent fix can be implemented.