[Issue] How to configure orchestrator (metaAgent) after GA

[yuriwoof]

Issue Description
In the previous SRE Agent portal, I was able to modify the orchestrator (metaAgent).

However, after GA, when I created a new SRE Agent, the corresponding configuration menu was no longer available.

Thread ID
Paste the thread ID from the SRE Agent portal
(e.g., 50f7521d-dfee-487e-9188-5abdc8adde91)

Steps to Reproduce

1. Create new SRE Agent after GA

Expected Behavior
Enable to configure orchestrator (metaAgent)

Actual Behavior
Unable to configure orchestrator behaviour

[yuriwoof]

I played newer UI bit around and find I can realize this with creating named "meta_agent".

[sanchitmehta]

Thank you for reporting this!
With the GA release, direct orchestrator (metaAgent) configuration is no longer exposed as a standalone setting. The GA architecture uses a managed orchestrator that automatically routes requests to the right agent - and the way to customize behavior is now through Custom Agents (sub-agents).

What are Custom Agents?
Custom agents are specialized domain experts that you define with their own instructions, tools, and capabilities. When a user's request matches your custom agent's domain, the built-in orchestrator automatically hands off to it. This effectively replaces the need to modify the orchestrator directly — your custom agent is your custom behavior.

Each custom agent can:

• Have its own system prompt/instructions defining expertise and behavior
• Inherits the default Orchestrator tools but overrides with select-system-tools/custom tools (Kusto queries, Python code execution)
• Connect to MCP servers (Model Context Protocol) to bring in third-party tools
• Inherits the default Orchestrator skills but override with select skills