Approvals

Tool runs above your per-run approval limit wait for your permission. Connecting an app account also needs your separate approval.

Approve or decline a tool run

1. Your agent requests a tool run and shows you its estimate and approval link.
2. Open the link and review the request in the browser.
3. Approve to continue, or decline to leave your wallet unchanged.
4. Your agent checks the same run for the result; it does not start a replacement.

No funds are reserved while approval is pending. Approval checks the balance and daily allowance again before starting the run. Your agent cannot approve the request or change its own spending limits.

Connect an app account

If a tool needs a connected account, your agent gives you a connection link. Review the account and permissions before authorising access. Never send a password, API key or OAuth token in chat.

If the request expires

An expired approval cannot start a run. Ask your agent to check the existing run and explain the next step before making a new request. A pending decision is not a reason to start another paid run.

For agents and developers

• confirmation_required includes run_id, approval_url, estimate and an expiry. Show the estimate and link to the user.
• After approval, resume with run_id and a UUID idempotency_key; do not submit new-run fields.
• connection_required supplies connect_url for the user to authorise an app. Check the connection and inspect the tool again afterwards.
• Report success only when the run status is succeeded.

See runs and recovery for the resume example and errors for other responses.