Review actions and keep control
Set the boundary before work starts, review any approval request, and check what actually happened before repeating or taking over an action. Human oversight is a working practice supported by controls—not a promise that every operation will always produce a confirmation dialog.
On this page
These controls describe the October 2026 development interface. Approval behavior depends on the operation, policy, account and release. AgReady's broader Agent Ready vision should not be read as a guarantee that every business system has a fully implemented human-takeover mode today.
State the boundary in the task
Separate reading from changing and preparing from sending. For example:
Prepare a draft reply using the supplied notes. Show it in this conversation. Do not send it, update the account or publish anything. Ask me before any external action.
Name the allowed resources and the output you want. Configure appropriate access and policy controls as well: a written instruction is important, but it is not a technical substitute for limiting account permissions.
Read an approval request
When Tool execution requires approval appears:
- Confirm the tool and requesting session. A forwarded request may concern another session's actual action.
- Read the operation preview. Where shown, inspect the command, working directory, recipient, subject or content.
- Check resource scope and allowed destinations, not just the risk label.
- Decide whether the exact action is within your intent and whether the displayed information is sufficient.
- Approve only an appropriate scope, or Reject and explain what must change.
A vague or unexpected request is a reason to clarify, not to approve so that the task can continue.
Choose the narrowest useful scope
Depending on the request, the interface can offer Allow once, Allow for this task, or Allow for this session. Only the scopes allowed by that request are shown.
Prefer one-time approval when you only intend the displayed action. Before allowing reuse, inspect the resources to which that reusable approval applies. A session-wide choice should not be made merely to avoid future interruptions.
Approval is permission to attempt an operation; it is not evidence that the operation succeeded. After the decision, inspect the resulting status and output. If submission fails or the result is uncertain, check the pending request before deciding again.
Do not rely on a dialog for every action
The product evaluates approval policies and some operations can proceed without an interactive prompt. Do not assume that an absent prompt means the operation was harmless, or that a low-risk label replaces your review. Use account permissions, appropriate policy and a narrowly scoped task together.
The Approvals page can help you inspect requests and records associated with your user. It is not a replacement for checking the affected external system when delivery or a write is uncertain.
Stop and take over without duplicating work
Use Stop current run when you need to interrupt an active run. Stopping is not a rollback, and it does not establish that all queued work or external effects disappeared.
Before acting manually:
- Inspect the latest status, messages and tool results.
- Identify what is completed, still pending and uncertain.
- For an external action, check the actual destination or account when appropriate. Do not send the same message again merely because the conversation stopped.
- Tell the agent that you are handling the remaining step and specify that it must not repeat it.
- If you later resume, state what you completed and what is still authorized.
This is a safe handover procedure, not a claim of a universal “take over every connected app” button. Where the outcome cannot be determined, pause the dependent action and ask the administrator or service owner to help establish the state.
Review the deliverable too
Permissions and successful tool responses do not prove that a result is correct. Compare facts, recipients, amounts, filenames and scope with the original request. Keep approval of an action separate from acceptance of its output.
See the Agent Ready vision for the broader direction, or sessions and context for session lifecycle controls.