Timeout Means No — The One Rule That Makes AI Agent Approval Gates Actually Work

Description and use

The "timeout means no" rule prevents pipeline stalls and ensures that unapproved actions are safely rejected.

Problem

When an AI agent performs irreversible actions, a lack of human response can leave the system in an unsafe or stalled state, causing missed opportunities or unintended behavior.

Outcome

The "timeout means no" rule prevents pipeline stalls, reduces notification fatigue, and ensures that unapproved actions are safely rejected. It also provides a clear audit trail and a health metric for gate usage.

Workflow

• 1. Bot sends an approval request with the full intent, reasoning, and a deadline (e.g., "Reply by 03:14 or this is rejected.")
• 2. If no reply, send one reminder at the halfway mark.
• 3. If deadline passes with no reply, automatically reject the intent, log the outcome as "rejected_timeout", and include it in the next morning briefing.
• 4. The pipeline continues to the next job immediately, never blocking on the pending approval.

Evidence

If I don't answer, the answer is no.

Source

The queue never blocks on an approval. The next job runs immediately.

Source