Approval Agents

Approval Agents add a mandatory human-in-the-loop gate before any cloud agent can execute destructive or high-risk actions. Define policies — agents ask for permission, humans approve or deny.

How it works

When an agent is about to take an action that matches an approval rule:

  1. Agent pauses and sends an approval request to the configured approvers.
  2. Approvers receive a notification (email, Slack, or mobile push).
  3. They review the proposed action with full context — what the agent wants to do and why.
  4. They approve or deny. Agent proceeds or stops based on the decision.
  5. The approval decision is logged in the audit trail.

Approval gates add latency to agent runs. Use them for high-risk actions (production deployments, database migrations, security changes), not routine coding tasks.

Approval rules

Define approval rules in .vyre/approvals.yaml:

yaml
# .vyre/approvals.yaml
approval_rules:
  
  - name: "Production deployment"
    trigger:
      tool: run_command
      command_matches: "kubectl apply|helm upgrade|vercel --prod"
    approvers:
      - team: "platform-team"
      - role: "senior-engineer"
    require_count: 1
    expiry: "1h"
  
  - name: "Database migration"
    trigger:
      tool: run_command
      command_matches: "prisma migrate deploy|alembic upgrade|flyway migrate"
    approvers:
      - user: "db-admin@company.com"
    require_count: 1
    expiry: "30m"
  
  - name: "Secrets access"
    trigger:
      tool: read_file
      path_matches: "**/.env*|**/secrets/**"
    approvers:
      - role: "security-team"
    require_count: 2

Review queue

Approving from Slack

If Slack is connected, approval requests are posted as interactive Slack messages. Approvers can click "Approve" or "Deny" directly in Slack without opening the Vyre UI.

Approving from mobile

Approval requests trigger push notifications on the Vyre mobile app. Tap the notification to see the full context and approve or deny from your phone.