request_escalation
Hands a hard task to the power tier.
Only offered when a power model is set, auto routing is on, the trigger is on and no tier is pinned. The power model gets the whole chat and answers in three parts. If it fails, the everyday model does the task.
- Tool name
- request_escalation
- Group
- Routing
- Risk
- low
- Needs approval
- never
- Approval rule
- No approval.
- Allowed in scheduled jobs
- No
- Default
- on
Parameters
| Name | Type | Required | Default | Meaning | Limits |
|---|---|---|---|---|---|
| reason | string | Yes | Why a stronger model is needed. | ||
| task | string | No | The task to hand over. |
Returns
The power model's answer.
Example (made up for this page)
{
"reason": "demo"
}Result: ... Summary: ... Context: ...Side effects
- Makes one or more calls to the power model and saves a handoff file.
How it can fail
| When | What the agent sees |
|---|---|
| Not available | Escalation is not available. |
See also:Routing tools
Checked against the source at commit f4fd89f on 29 Oct 2026. Everything here is merged on the main branch; no release has been tagged yet. The source is private, so these pages are the public description.