GitHub user joeyutong added a comment to the discussion: [Feature] Sub-agent Resource for Flink Agents - Framework part
Thanks for the clarification. I think we are aligned on the implementation architecture. What you describe as `InternalSubagent` is essentially the framework-provided implementation of the internal **call protocol** that I mentioned above. It also clarifies the distinction between the underlying `Agent`, which users author, and the caller-side invocation capability, which the framework provides for an internal agent. > Subagent is the common interface for all sub-agents. Both external > (SubagentSetup) and internal sub-agents implement it. My remaining concern is how this distinction is represented in the public API. While `call()` is a natural contract for an external integration, the proposal applies the same public `Subagent` abstraction to internal agents. An internal `Agent` author does not need to implement `call()`, but `call()` still becomes part of how the internal subagent is publicly represented, even though it is a framework-provided capability rather than part of the `Agent` authoring contract. Therefore, my concern is not with the `InternalSubagent` implementation. This is why I characterized the shared interface as being closer to `SubagentInvoker`: not necessarily to prescribe a particular solution, but to emphasize that, for an internal sub-agent, the interface describes a framework-provided invocation capability rather than part of the `Agent` authoring contract. GitHub link: https://github.com/apache/flink-agents/discussions/909#discussioncomment-17671555 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
