Skip to content

Deny Unanswered

DenyUnanswered denies approval-required calls and unanswered AskUser questions with readable results, so a run nobody attends finishes instead of pausing on DeferredToolRequests.

Deferred calls exist for a caller who answers them in a second run. In an unattended run nobody ever will: approvals wait on a person who is not there, questions wait on a user who left, and the run ends with DeferredToolRequests. DenyUnanswered ends the wait inside the run:

  • A held approval is denied with message (ToolDenied).
  • A deferred AskUser question, including one whose tool PrefixTools renamed, is answered with question_message, which says nobody is available to answer rather than that the user declined.

Any other deferred call stays deferred for its own handler. Without DenyUnanswered, nothing changes.

Source

While Pydantic AI Harness is on 0.x releases, the API may change between minor releases; when it does, deprecation warnings and release-note migration guidance tell you (or your agent) exactly how to upgrade. See the version policy.

flowchart TB
    accTitle: Deny Unanswered: deferred calls nobody attended get results inside the run
    accDescr: The model's tool calls include deferred calls. Earlier handlers, such as HandleDeferredToolCalls or an approval handler, get the first say. DenyUnanswered runs innermost on what is left: it denies held approvals with message and answers ask_user_question calls with question_message, and the run continues with those results. Any other deferred call stays deferred. SubAgents and DynamicWorkflow child runs get the parent's DenyUnanswered.
    model(["model"])
    earlier["earlier handlers<br/>HandleDeferredToolCalls,<br/>approval handler"]
    deny["DenyUnanswered()<br/>innermost"]:::capability
    other["other deferred calls<br/>stay deferred"]
    child["SubAgents and<br/>DynamicWorkflow<br/>child runs"]
    model -->|"deferred calls"| earlier
    earlier -->|"what is left"| deny
    deny -->|"ToolDenied(message),<br/>question_message"| model
    deny -.->|"not an approval<br/>or ask_user_question"| other
    deny -.->|"forwarded to"| child
    classDef capability stroke:#E520E9,stroke-width:2px

Usage

from pydantic_ai import Agent
from pydantic_ai_harness import AskUser, DenyUnanswered

agent = Agent(
    'anthropic:claude-sonnet-5-5',
    capabilities=[
        AskUser(answerer=None),  # no answerer: every question is deferred
        DenyUnanswered(),
    ],
)

Use message and question_message to change the text the model sees for a denied approval and an unanswered question:

from pydantic_ai_harness import DenyUnanswered

deny = DenyUnanswered(
    message='No one is on duty, so the request was not approved.',
    question_message='No one is on duty to answer; pick a safe default and say which one.',
)

Forwarding to children

SubAgents delegations and DynamicWorkflow child runs carry the parent run’s DenyUnanswered into the child’s capabilities when it is present, so a delegate that asks a question or requests approval is denied inside the child run too, and the delegation finishes instead of returning a pending child. The handler runs innermost, after every handler that may ask the user, so a present human still wins.

This forwarding is specific to DenyUnanswered for now: a general way for capabilities to pass themselves on to child runs is being designed in #13135 and will replace it.

Two kinds of delegation do not receive the parent run’s capabilities, so nothing is forwarded there and the child keeps its own behavior: one that a durable engine runs as a tool activity, such as a named sub-agent under TemporalDurability, and a remote sub-agent that a SubAgentWorker runs for TaskControl(remote_agents=...). Give such a child, or the worker’s agent, its own DenyUnanswered when it should deny too.

Telemetry

Emits nothing into telemetry.

API reference

DenyUnanswered

Bases: AbstractCapability[AgentDepsT]

Deny approval-required calls and unanswered questions that nobody attended.

For runs that may end with no one available to approve or answer: a held approval is denied with message, and a deferred AskUser question is answered with question_message, so the run finishes instead of pausing on DeferredToolRequests. Any other deferred call stays deferred for its own handler. Without this capability nothing changes.

Emits nothing into telemetry.

Attributes

message

The tool result for a denied approval.

Type: str Default: DEFAULT_MESSAGE

question_message

The tool result for an unanswered AskUser question.

Type: str Default: DEFAULT_QUESTION_MESSAGE

Methods

get_ordering
def get_ordering() -> CapabilityOrdering

After every handler that may ask the user, including any HandleDeferredToolCalls subclass.

Returns

CapabilityOrdering

handle_deferred_tool_calls

@async

def handle_deferred_tool_calls(
    ctx: RunContext[AgentDepsT],
    *,
    requests: DeferredToolRequests,
) -> DeferredToolResults | None

Deny the calls nobody attended.

Returns

DeferredToolResults | None

DEFAULT_MESSAGE

Default: 'No one was available to approve it, so it did not run.'

DEFAULT_QUESTION_MESSAGE

Default: 'No one is available to answer in this run; continue without the answer.'