Choose autonomy to match the task
Reading the project is sufficient for initial familiarization. Draft mode fits preparing content without making it public. Approval-based publication helps when the owner or editor needs to check wording, facts and links. Autopilot is appropriate after the process is agreed: the agent performs only allowed operations in specified sections. One mode does not automatically replace another. For example, a technical publish button does not mean the current client is entitled to use it. Stricter project and individual connection restrictions remain in force.
Set specific boundaries
The policy can specify permitted sections, actions and daily limits. A new autopilot's baseline setting limits work to one new page and five edits per day in /answers/. Check the actual saved values before starting. Agree with a client on which pages are created, where facts come from and what requires manual decisions. The mode does not provide arbitrary DNS, banking or repository access. If file installation needs external access, the owner grants that separately in the executor's environment, not through AURA's policy itself.
What approval looks like in practice
Suppose the agent prepares a page about choosing a service. In approval-based publication mode, it creates a request and returns a review link. The owner sees the proposed action, content comparison and verification details. After a decision, the agent reads the status and continues only the permitted part of the process. Awaiting approval must not be labeled successful publication. Consent for one article also cannot count as permission to rewrite the entire website. After execution, check the public URL and action record: they show precisely what was done and when.
Keep the ability to stop and inspect
The log retains completed, rejected, failed and pending actions. This distinguishes prepared changes from applied ones. On failure, investigate the cause first rather than increasing access to the maximum. If the process is no longer needed, restrict the policy or revoke the connection. An external agent's execution schedule is configured separately and does not arise from selecting the word ‘autopilot.’ Good automation retains a clear outcome for each operation and leaves the owner one specific step when continuation requires their consent or account.
Conditions and limitations
- Autopilot is not a background executor
- Limits and policy do not override connection permissions
- Approval applies to a specific action
Explore the details
The agent performs authorized actions with a log and owner oversight
Configure autopilot rules