Bound runtime work

Set limits before launching a long run: model steps, tool duration and concurrency, worker concurrency, environment resources, evaluation trials and any cost budget your configured pricing can support.

Bound execution separately from spend

CayuConfig owns process-wide defaults. RunRequest owns permitted per-run overrides. A maximum step count bounds runtime iterations; it is not a complete monetary estimate. A tool can perform expensive external work independently of model tokens.

Use the configuration reference to find the exact field owner and default. Do not create additional ambient environment switches in tools for settings already owned by typed runtime configuration.

Account with available evidence

Pricing, usage observation and budget reservation/settlement have distinct roles. Configure an applicable price book before claiming a hard cost limit. Unavailable usage or pricing is not zero cost. Evaluation launch reports distinguish hard-bounded exposure from observed-only cost.

Test exhausted limits, unavailable pricing, child work and interruption. Verify that reservations and terminal evidence settle under the selected policy, including an ambiguous external outcome.

Reference: budget API, run configuration and evaluation launch.