Goal
We have several standalone Rovo agents built by different teams (for example an IT helpdesk agent and a GTM apps support agent), each with its own instructions, knowledge sources and owners. We want a single "master" agent that only routes the user's question to the right one.
What we tried
In Rovo Studio, under the master agent's Subagents section, selecting "Add subagent" opens a form with only a Name, Trigger and Instructions. We couldn't find a way to select an existing agent from our site. The docs say subagents have their own instructions, knowledge and tools and don't inherit anything from the parent (https://support.atlassian.com/rovo/docs/add-scenarios-to-a-rovo-agent/). They don't say whether an existing agent can be used.
What works
A router with inline subagents works in our tests: a matching trigger hands off to the subagent, and an unmatched message gets a fallback reply. It only behaved as a pure router once we removed all knowledge sources from the parent (otherwise it answered from company knowledge itself), and we had to set the subagent output mode to "must use exact output" so the reply wasn't reworded.
The problem
Recreating each agent inside the master means two copies of every agent's logic. The original agent owners lose ownership, and the copies can drift out of sync.
Questions
- Is there a supported way to select an existing (published) agent as a subagent, or to have a parent agent call another agent?
- If not, is it planned? Is there a Jira ticket we can follow?
- What do others use instead: Automation chaining with {{agentResponse}}, a thin router that only points users to the right agent, or something else?
Thanks!
See pic, I can only create "new" agents as subagents, I want to be able to choose from an existing agent:
