Feature · Work

Escalations

Resolve questions with the options and evidence workers found.

Last changed

Generated from commit be57775 ·

How it works

Why workers escalate

The reasons are: ambiguous requirements, conflicting requirements, missing information, missing permission, low confidence, a guard tripped, a loop detected, repeated failure, budget exhausted, a policy conflict and high risk.

Answer an escalation

Open Escalations. Pick an option, or write your answer. Select Resolve. When the escalation blocks the work, the button is Resolve and resume. Members and above can resolve.

Where escalations go first

A worker's question goes to its manager first. It reaches you only when the manager cannot settle it.

A budget escalation

When a work item reaches its budget, it pauses with the escalation "Budget exhausted on" and the item key. Choose Raise the budget to resume from the last checkpoint, or Stop the work. You lose no progress. See Out of budget.

From the help article Escalations, checked against the product on .

What you can do

The operations this feature's screens call. Each one is POST /api/<name>, and the badge says who may call it.

  • listEscalations

    Viewer

    Lists escalations.

    Types: ListEscalationsRequest returns PageResponse<EscalationDto>

  • resolveEscalation

    MemberNo API tokens

    Resolves the escalation.

    Types: ResolveEscalationRequest returns EscalationDto

  • getEscalationRoute

    Viewer

    Gets the escalation route.

    Types: GetEscalationRouteRequest returns GetEscalationRouteResponse

  • retryEscalationDelivery

    Member

    Retries the escalation delivery.

    Types: RetryEscalationDeliveryRequest returns GetEscalationRouteResponse

  • explainAction

    Viewer

    Explains the action.

    Types: ExplainActionRequest returns ExplainActionResponse

  • explainDecision

    Viewer

    Explains the decision.

    Types: ExplainDecisionRequest returns ExplainDecisionResponse

  • listEvents

    Viewer

    Lists events.

    Types: ListEventsRequest returns PageResponse<AuditEvent>

  • getContextManifest

    Viewer

    Gets the context manifest.

    Types: GetContextManifestRequest returns GetContextManifestResponse

Screens

What it records

The feature writes these events to the audit log, the permanent record of what happened.

  • Escalation delivered

Generated from code at commit be57775 ·

Turn the numbers into shipped work.

Agent runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.