openclaw - 💡(How to fix) Fix Fallback routing defaults to main agent — privacy leak and wrong behavior [1 participants]

• Fail explicitly with a clear error ("agent not found")

TL;DR

Configure a catch-all agent or implement an explicit error handling mechanism to prevent the gateway from falling back to the main agent when a message is routed to an unavailable agent.

Guidance

• Identify the routing configuration that causes the fallback to the main agent and modify it to either fail explicitly with an error or route to a configurable catch-all agent.
• Review the binding points to ensure they are correctly configured and point to existing agents.
• Consider implementing a validation mechanism to check the existence of agents before routing messages to them.
• Evaluate the possibility of introducing a new configuration option to specify a catch-all agent or an error handling behavior.

Example

No code snippet is provided as the issue does not contain sufficient technical details about the implementation.

Notes

The solution may require modifications to the OpenClaw configuration or the underlying routing logic. The exact implementation details are not provided in the issue, so a more detailed analysis of the codebase and configuration is necessary.

Recommendation

Apply a workaround by configuring a catch-all agent or implementing an explicit error handling mechanism, as upgrading to a fixed version is not mentioned as an option in the issue. This approach allows for a more controlled and flexible handling of misrouted messages.