[Feature Request] Support Multi-Agent Routing from Single Channel Endpoint

[mikeop5439]

Summary

Support routing messages to different agents from a single channel endpoint.

Component(s) Affected

• Core / Backend (app, agents, config, providers, utils, local_models)
• Console (frontend web UI)
• Channels (DingTalk, Feishu, QQ, Discord, iMessage, etc.)
• Skills
• CLI
• Documentation (website)
• Tests
• CI/CD
• Scripts / Deploy

Problem / Motivation

Currently, one channel instance can only bind to one agent. When integrating with external platforms that have multiple bots or robots, users must deploy separate QwenPaw instances for each agent.

Proposed Solution

Enable a single channel to distribute incoming messages to different agents based on message metadata.

Alternatives Considered

1. Deploy multiple QwenPaw instances
2. Use chat_with_agent tool for forwarding
3. Use external reverse proxy for routing

Additional Context

Current behavior: All messages from a channel are processed by the same agent.
Expected behavior: Messages can be routed to different agents based on their properties.

Willing to Contribute

• I am willing to open a PR for this feature (after discussion).

[github-actions]

Welcome to QwenPaw! 🐾

Hi @mikeop5439, thank you for your first issue!

We'll review your issue soon. Thank you for supporting QwenPaw!

---

Tip

⭐ If you find QwenPaw useful, please give us a Star!

Staying ahead

Star QwenPaw on GitHub and be instantly notified of new releases.

Your star helps more developers discover this project! 🐾

[LUOSENGWA]