Subagents
When a request is complex, Blaze’s AI can decide on its own to spin up a “subagent” — a separate instance of itself — and hand off part of the investigation or work to it. This page explains what’s happening when you see a subagent running during a conversation.
1. What is it?
A subagent is a mechanism where Blaze’s main AI delegates part of a complex request to a separate AI instance.
For example, for a request like “look into how several objects are configured, then implement the change”, Blaze may split the work like this:
-
Hand off the investigation to a subagent, which checks the relevant files and metadata
-
Take the results back and use them in the main AI’s implementation or response
Whether a subagent is used is decided automatically by the AI — there’s nothing you need to trigger or operate yourself.
2. What you’ll see in the conversation
While a subagent is running, it appears as a block in the timeline, just like any other tool execution (file edits, running a command, and so on).
-
The block’s title shows a short description of what it’s investigating or doing
-
Opening the block shows the subagent’s log — what it said and which tools it used
If you notice extra blocks you don’t recognize, there’s no need to worry — Blaze is simply splitting the work behind the scenes.
3. Safety
-
A subagent runs through the same mechanism as the main conversation (the same tools, the same rules). If it needs to perform an operation that affects your org, a confirmation is required just like in a normal conversation. See Approval Mode for details
-
A subagent can call further subagents, but there’s a limit to how deep this nesting can go — it can’t grow without bound
4. Settings
There’s no setting to turn subagents on or off individually. The AI decides automatically whether to use one, based on the request.
If the behavior isn’t what you expected, or the investigation or changes seem to be going further than intended, you can add follow-up instructions mid-conversation to narrow the scope of the work.