Approvals
Agent HQ includes an approval workflow for tasks that involve sensitive operations. This keeps a human in the loop for high-risk changes.
How approvals work
Section titled “How approvals work”Tasks can be flagged as requiring approval. When flagged, they enter a blocked state and wait for a human to approve or reject them.
Approval statuses
Section titled “Approval statuses”| Status | Meaning |
|---|---|
| Pending Review | Task is waiting for human review |
| Approved | Human approved the task — execution continues |
| Rejected | Human rejected the task — execution stops |
Dangerous mode
Section titled “Dangerous mode”Tasks can be flagged with dangerous mode when they involve risky operations such as:
- Modifying production configuration
- Deleting data or resources
- Running destructive commands
- Accessing sensitive systems
Dangerous mode tasks always require approval before execution proceeds.
Reviewing approvals
Section titled “Reviewing approvals”Tasks pending approval can be found by checking the task board for tasks in a blocked status. For each pending task, you can:
- Review — see what the task will do (title, body, context)
- Approve — let the task proceed
- Reject — cancel the task
Best practices
Section titled “Best practices”- Enable approvals for tasks that modify production systems
- Review the task body and context before approving
- Use dangerous mode sparingly — it adds friction to the workflow
- For trusted, well-tested operations, consider disabling approval requirements