Review at the moment of action
The decision appears when Toyo knows the specific operation, target, and reason, rather than asking for blanket permission at setup.
Sensitive actions · Approval controls
Let consequential changes wait for you.
Review before execution
Risky file, browser, memory, connected-account, and sandbox change-set actions can surface explicit approval cards before execution.
Review at the moment of action Accept or reject clearly Cover more than files
Outcomes
Control at the moment it matters.
In the product
Choose the operating mode before the next tool call.
Decide when Toyo may act automatically and when a specific operation must wait for review.
Agent, Research, and Chat establish the available capability surface. Auto-execution is a separate, clearly marked choice, while guarded browser submissions still keep explicit approvals.
Agency controls01 02 03
Accept or reject clearly
Approval cards make the pending action visible and give the user a direct choice before the guarded operation proceeds.
Cover more than files
The same control model extends to sensitive browser steps, memory suggestions, external Google writes, and sandbox synchronization.
How it works.
Approval controls keep routine reading and analysis moving while reserving a deliberate pause for higher-impact operations.
- 01
Toyo prepares the action
The agent reaches a step that requires a protected mutation or sensitive interaction.
- 02
Review the pending card
Inspect what will happen, where it will happen, and which workflow requested it.
- 03
Accept or reject
Approve the operation to continue or reject it while keeping the surrounding task visible.