openclaw - 💡(How to fix) Fix [Feature]: OpenClaw 跨会话/跨 Agent 互通问题 [1 comments, 2 participants]

TL;DR

To address the OpenClaw cross-session and cross-Agent communication issues, consider implementing a mechanism for sessions_send to communicate with sub-Agents and provide real-time status updates.

Guidance

• Implement a communication mechanism between the main Agent and sub-Agents, allowing the main Agent to monitor sub-Agent progress and intervene when necessary.
• Provide a way for the main Agent to receive real-time status updates from sub-Agents, such as through a subagents(action="status") API.
• Consider adding automatic retry or resume capabilities for sub-Agents that abort, to prevent task chain breakage.
• Investigate preserving the last state of a sub-Agent after abortion, to allow for resumption from the breakpoint.

Example

No specific code example can be provided without further context, but a potential solution might involve modifying the sessions_send API to accept a sub-Agent ID and message, and implementing a callback event for sub-Agent status updates.

Notes

The provided issue description lacks specific technical details, making it challenging to provide a comprehensive solution. However, the suggested guidance points should help address the core issues of cross-session and cross-Agent communication.

Recommendation

Apply a workaround by implementing a custom communication mechanism between the main Agent and sub-Agents, as the existing sessions_send API seems insufficient for this purpose. This will help mitigate the issues until a more comprehensive solution can be developed.