openclaw - 💡(How to fix) Fix Support concurrent user turns during long-running tool execution [1 comments, 2 participants]

TL;DR

Implementing concurrent turns or an interrupt signal can help address the issue of queued user messages during long-running tasks.

Guidance

• Consider Option 1: Gateway-level concurrent turns, which allows multiple active turns per session, enabling new turns to reference background task IDs via existing session state.
• Explore Option 2: Interrupt signal, where a user message during an active turn cancels or suspends the current turn and starts a new one, preserving context.
• Evaluate the feasibility of Option 3: Background result channel, where sessions_spawn / exec results are delivered as separate system events, rather than blocking the turn.
• Assess the trade-offs between these options, considering factors like complexity, performance, and user experience.

Example

No code snippet is provided, as the issue description does not include specific implementation details.

Notes

The choice of solution depends on the specific requirements and constraints of the system, including performance, scalability, and user experience considerations. It is essential to evaluate the trade-offs between the proposed options and consider potential edge cases.

Recommendation

Apply a workaround, such as implementing Option 1: Gateway-level concurrent turns, as it seems to be a more feasible and flexible solution, allowing for multiple active turns per session and enabling new turns to reference background task IDs.