openclaw - 💡(How to fix) Fix [Feature]: Add configurable Gateway CLI timeout and session isolation [2 comments, 2 participants]

TL;DR

Implementing a configurable gateway-level timeout for CLI agent calls, such as adding a gateway.timeout.cli parameter, is likely to mitigate the main session contention issues.

Guidance

• Review the proposed solution options, focusing on adding a gateway.timeout.cli configuration to increase the timeout value beyond the current ~30s RPC layer timeout.
• Consider the trade-offs between the proposed options: Option 1 for a short-term fix, Option 3 for a medium-term solution, and Option 2 for a long-term architectural change.
• Evaluate the impact of each option on backward compatibility, severity, frequency, and consequence of the issue, as outlined in the impact assessment table.
• Verify the effectiveness of any chosen solution by monitoring the behavior of CLI calls under heavy load and checking for improvements in timeout issues and session contention.

Example

{
  "gateway": {
    "timeout": {
      "cli": 300
    }
  }
}

This example illustrates how to add a gateway.timeout.cli parameter to the openclaw.json schema, as proposed in Option 1.

Notes

The choice of solution depends on the specific requirements and constraints of the system, including the need for backward compatibility and the severity of the issue. It's essential to carefully evaluate each option and consider potential side effects before implementing a fix.

Recommendation

Apply Option 1 (add gateway.timeout.cli configuration) as a short-term workaround to quickly address the issue, given its simplicity and compatibility with the current system.