Skip to main content
Use this pattern when your application needs more than a one-shot task: a budgeted mission, tool calls, approval, resumable events, and a durable audit trail.

Example applications

  • A support copilot that drafts a reply but requires approval before sending.
  • A finance workflow that caps tool calls and elapsed time.
  • A coding assistant that streams progress and preserves a resumable audit.
  • An operations agent that refuses new work while a prior effect is unresolved.

Use these contracts

Verification

Test an accepted mission, wrong-scope token, revoked token, exact idempotent replay, body conflict, interrupted SSE connection, approval refusal, budget exhaustion, and terminal readback. Keep each proof distinct.

Mission lifecycle tutorial

Build the complete create, observe, resume, and verify flow.
Last modified on August 14, 2026