Provider interaction responses and retries

When an agent awaits external interaction, submit a response or cancellation with the interaction request identifier, then read the original task to confirm the result.

provider_interaction.required may occur while a task is still working; do not always require input-required. moi.provider_interaction.respond uses version:1, the original requestId, and target agentId/contextId/taskId. target must match the current message and task ownership. Supply either a non-null payload or cancelled:true, exclusively.

{"type":"moi.provider_interaction.respond","version":1,"requestId":"interaction-example","target":{"agentId":"agent-example","contextId":"conversation-example","taskId":"task-example"},"cancelled":true}

Canceling an interaction does not cancel the entire task. moi.provider_interaction.received only acknowledges receipt of the interaction submission/cancellation; continue reading the original task. The browser handoff completion payload currently contains only completed:true. Validate question-and-answer interactions against the original questions; do not use one payload for every interaction type.

Current Astra upstream retry classification

Upstream result

Current owner behavior

Documentation guidance

Already resolved

Replay succeeds without resubmitting to the Provider

Read the current interaction and task; do not change requestId to create a new operation.

Already claimed with unknown result, including 408/5xx/network errors

Do not resubmit; wait for the resolved event

A timeout does not prove nonreceipt. Retain the original request rather than immediately resending with a new ID.

Explicit 429

Record throttling and allow competition for a new attempt

This does not guarantee the product endpoint returns HTTP 429. Follow the actual product error and recovery conditions.

Explicit rejection by another 4xx

Persist the rejection; subsequent requests converge to rejection

Do not blindly repeat the same answer.

This classifies upstream/owner behavior, not public JSON-RPC HTTP status mappings. Current general error mappings may not preserve these upstream classifications; the real contract still needs verification. Default-runtime and Astra branches differ. A test of one Provider cannot establish behavior for all Providers.

Last updated on