GitHub user wenjin272 added a comment to the discussion: [Discussion] Supervisor + Sub-Agent Orchestration: Concrete Multi-Agent Use Cases for Event-Driven Agents
Hi, @weiqingy. Actually, we’ve recently received some requests for sub-agents and are currently considering how to address this within flink-agents. This work is being handled by other colleagues at the moment, but I’d like to share what I know about it. Recently, the Flink community initiated a discussion on [FLIP-577](https://lists.apache.org/thread/l5obwo4kvjblqnx24btsv4rwjwoflb6d), aiming to lay out a direction for evolving Flink into a data engine that natively supports AI workloads. It mentions the hope of introducing a new [RpcOperator](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=421957275#FLIP577:AINativeFlink%E2%80%94AnUmbrellaProposalforMultimodalDataProcessing-FLIP-XXX:SupportingRpcOperator%E2%80%94IndependentlyDeployedandScaledRPCServiceOperators) in Flink, which is independently deployed outside the stream graph and can communicate with operators within the stream graph via RPC. @xintongsong shared in community discussions his view that RpcOperator can help flink-agents [implement sub-agent capabilities](https://lists.apache.org/thread/5kso2jgtzpd6g4wrknqbg5sm4g16fkhc). I believe this discussion is highly beneficial for clarifying the requirements and design of multi-agent systems. Thank you for your insights, and I will also invite my colleagues to join this discussion. GitHub link: https://github.com/apache/flink-agents/discussions/660#discussioncomment-16888612 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
