Adding Manual Approval Gates to AI Agents
sekyr95 · reddit · 2026-07-13
The author built an MCP server to add a structured gate for agents, ensuring actions "must be approved by a human before execution." ### How it works - The agent first calls `impri_push_action` to submit the pending action - The request enters an approval inbox with a status of 'pending' - Humans can view, approve, reject, or even edit the text first - The agent waits on `impri_await_decision` and can only continue execution upon receiving 'approved' ### Design motivation The author emphasizes that this is not simply writing "please confirm first" in the system prompt, as models might bypass it. Instead, it makes approval part of the process structure, genuinely halting the agent before execution. ### Other info - Supports Slack / Discord / Telegram button approvals - Includes an audit log recording who approved what - Exposed via a REST API, and can also be used from MCP clients like Claude Code, Cursor, and Desktop - The project is open-source under the MIT license, prioritizes self-hosting, and offers an early hosted version The author admits the project is still in its early stages with few real users, primarily gathering feedback, especially on "where human intervention points should be placed."
Related event: New MCP Server Adds Human-in-the-Loop Approval for AI Agents(2 posts)→
More from coding & agent
- A one-page guide maps AI agents from core concepts to real-world use cases — goyalshaliniuk · 2026-07-21
- OxDeAI opensource protocol moves AI-agent policy checks before execution — docybo · 2026-07-21
- Kimi staff member builds a VR companion with Kimi Code K3 demo — dejavucoder · 2026-07-21
- Kimi K3 took 75 minutes and still failed a simple diagram task, user says — MinusKarma01 · 2026-07-21
- Coding agents need better rules for when to read search summaries or full pages — RhubarbLarge2747 · 2026-07-21
- Chart compares open tickets across Gemini, Codex, Claude, Grok and Opus 3 — nptacek · 2026-07-21