yunfengzhou-hub opened a new issue, #1141: URL: https://github.com/apache/flink-agents/issues/1141
### Search before asking - [x] I searched in the [issues](https://github.com/apache/flink-agents/issues) and found nothing similar. ### Description ## Motivation A parent agent and its subagent should not have to be implemented in the same language. Supporting a subagent registered in one language and invoked by a parent in the other lets teams mix Java and Python agents and reuse the existing cross-language resource bridge for subagents. ## Proposed scope - Serialize and reconstruct a subagent setup across the language boundary, and dispatch subagent call and status events through the pemja bridge, so a subagent setup defined in one language can be materialized and run in the other. - Support cross-language internal subagent invocation (Java parent to Python subagent, and Python parent to Java subagent) with memory isolation and durable state preserved across the bridge. - Support cross-language model-driven delegation (sub-agent as tool) where the subagent and the parent chat model are in different languages. - Keep cross-language behavior at parity with same-language usage. ## Acceptance criteria - Cross-language internal subagent invocation works end to end in both directions. - Cross-language model-driven delegation works end to end. - Reuses the existing cross-language end-to-end infrastructure (e2e-test/flink-agents-end-to-end-tests-resource-cross-language and the cross-language snapshots). - Docs describe cross-language subagent usage. ## Dependencies - AGENT resource type and Subagent API (#938). - Registering an Agent as an isolated, durable subagent (internal sub-agent), and LLM invocation of subagents (sub-agent as tool). - The existing cross-language resource bridge. - Tracked under the Subagent umbrella #1134; background #660, #909. ### Are you willing to submit a PR? - [ ] I'm willing to submit a PR! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
