[Agents] Post V1.0 Work

### What would you like to be added? This FR requests the implementation of a new SubAgent class: A re-usable component that manages LLM driven tool orchestration. This is applicable in the following contexts: * Allowing a Tool to iteratively solve a problem it encounters. For example, the EditTool using the SubAgent to find a better match string in the case of stale data; or a future "update docstrings" tool, which may call multiple existing tools to find files, edit them and test them. * Agentic Scopes - Allowing a Tool to be run in an isolated mode - If a tool doesn't manage its' own self healing, and instead expects to do that on the main thread, a SubAgent can be created, which clones the MonoAgent history, executes the tool, and only returns the successful response back to the main thread () This FR suggests the most direct path towards implementation would be: * Create a wrapper around GeminiChat which can drive the GeminiChat::sendMessage*(..) functions either in a nonInteractive, or Interactive function * Allow a list of filtered tools to be passed to the GeminiChat ContentGenerator::generateContentStream(..) function, so that only a subset of tools may be considered during execution * Allow a custom system prompt to be provided for GeminiChat to use. * Allow variable output via a set of private tools that the Agent can use to calculate response data to be accessed via the Caller of the SubAgent. ### Why is this needed? Currently, GC uses a _mono-agent_ arc

Posted by mainroach on Jul 3, 2025, 2:52 PM

Tags

• github (Other)

Related issues

• struct's lifetime requirements can be bypassed via covariant field assignment
• Proposal to Reorganize the Moderation Team and Review Moderation Policies
• Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
• proposal: container/...: generic collection types
• Better Custom Endpoint BYOK
• A concrete policy for backward compatibility until Godot 5.0