Approval controls determine when our AI Engineers may proceed with changes during a session. With the default workflow, the Engineer can perform supported inspections and present proposed changes for you to review. You can approve the pending work, decline it, or ask for a clearer explanation before deciding.
IN THIS ARTICLE
01 Review exactly what you are approving
Review the scope as well as the description of a change. Check which website or service is selected, what files or settings may be affected, and whether the proposal changes content, configuration, or stored data. For work with a meaningful recovery risk, confirm that the appropriate backup or staging copy exists before you approve it.
02 Understand the effect of Auto mode
Auto mode allows the Engineer to proceed with ordinary changes without pausing for each normal approval. This can help an experienced user complete a well-defined sequence, but it changes how much review happens before execution. In the Hosting AI Engineer, operations classified as destructive still require approval even when Auto is enabled. The WordPress Engineer has its own controls, so you should not assume that every potentially destructive WordPress action will always produce another confirmation in Auto mode.
We recommend keeping approvals enabled when learning the tools, working on a live business website, or asking for a task whose scope is not yet clear. Auto mode should follow a specific instruction and a recovery plan appropriate to the proposed work. It does not expand your account permissions or remove tool restrictions.
03 Decline a proposal or recover earlier work
Declining a proposal tells the Engineer not to apply the waiting changes. It does not reverse actions already completed earlier in the session. If you need to undo previous work, review the available Undo record or the correct backup restoration process for that particular change.
What do Go ahead, Don't and Run changes without asking mean?
- Read the proposed action and the affected site. Use See the change where available to review a file change.
- Choose Go ahead for the pending work you understand, or Don't when the proposal is unsuitable.
- Enable Run changes without asking only for a well-defined task with an appropriate recovery plan; turn it off when that scope ends.
The Hosting Engineer still requests approval for operations it classifies as destructive. Do not assume the WordPress Engineer adds a fresh confirmation for every risky action when automatic changes are enabled. Declining a pending proposal stops that proposal, not work already completed earlier in the session.