deepseek-ai/deepseek-harness · error

approval for escalating to "${mode}" was cancelled

Error message

approval for escalating to "${mode}" was cancelled

What it means

Error "approval for escalating to "${mode}" was cancelled" thrown in deepseek-ai/deepseek-harness.

Source

Thrown at packages/sandbox/sandbox/src/escalation.ts:185

  }
  if (approval.agent === undefined) {
    throw new Error(`sandbox escalation to "${mode}" requires approval, but the call has no agent to route it through`)
  }
  // Self-contained for the audit trail: approval/asked stores this reason,
  // and the target mode is part of the grant's identity.
  const outcome = await approval.approver.request({
    agent: approval.agent,
    toolName: approval.toolName,
    callId: approval.callId,
    reason: `escalate sandbox to ${mode}: ${justification}`,
    ...approval.signal ? { signal: approval.signal } : {},
  })
  switch (outcome) {
    // The schema enum already pinned `mode` to the closed target vocabulary;
    // the check above proved it is strictly wider.
    case 'allowed-once': return mode as SandboxMode
    case 'rejected': throw new Error(`the user rejected escalating this ${subject} to "${mode}"`)
    case 'cancelled': throw new Error(`approval for escalating to "${mode}" was cancelled`)
    case 'unavailable': throw new Error(`sandbox escalation to "${mode}" requires approval, but no approval channel is available`)
    default: return assertNever(outcome, 'EscalationOutcome')
  }
}

View on GitHub (pinned to b150a551b8)

Solutions

1. Re-request the escalation approval; the previous approval prompt was cancelled.

When it happens

Trigger: Thrown at packages/sandbox/sandbox/src/escalation.ts:185 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of deepseek-ai/deepseek-harness@b150a551b8 (2026-08-24). Data as JSON: /api/errors/06141d96df22e41c. Report an issue: GitHub.