openclaw - 💡(How to fix) Fix feat: make embedded Pi LLM-request timeout configurable [1 participants]

The error message suggests increasing agents.defaults.timeoutSeconds, but that config has no effect on the embedded path.

TL;DR

Increase the timeout for embedded Pi LLM requests by adding a configurable timeout setting, such as "timeoutMs": 60000, to the agents.defaults.embeddedPi configuration.

Guidance

• Review the proposed solution in PR #34673, which suggests adding a configurable timeout for embedded Pi LLM requests, to understand the potential fix.
• Consider testing the proposed configuration change to verify its effectiveness in resolving the timeout issue.
• Evaluate the current workaround of switching to faster provider models, such as google/gemini-3-flash, to determine if it is a viable temporary solution.
• Investigate the network latency introduced by the Claude MAX proxy to determine if there are any other potential optimizations or fixes.

Example

{
  "agents": {
    "defaults": {
      "embeddedPi": {
        "timeoutMs": 60000
      }
    }
  }
}

This example configuration snippet illustrates the proposed fix, which adds a configurable timeout setting for embedded Pi LLM requests.

Notes

The proposed solution was previously suggested in PR #34673 but was closed without merge, so it is essential to review and test the change thoroughly to ensure its effectiveness.

Recommendation

Apply the proposed workaround of adding a configurable timeout setting, as it directly addresses the identified issue and provides a clear solution.