Fighting approval fatigue: strip dangerous capabilities from tools instead of rubber-stamping
Glittering812 · reddit · 2026-10-15
A developer shares lessons on agent permission design: after adding approval steps, they caught themselves rubber-stamping requests without reading them. For destructive actions, they found it safer to remove the capability from the tool itself — if it can't delete, you don't have to catch every deletion request. Production deletes, payments, and prod deployments stay manual; anything quickly reversible runs autonomously. They ask the community which approvals they still keep versus replace with narrower permissions.
More from coding & agent
- Claude Code Pushes Urgent Security Update Across All Installations — umeshonai · 2026-10-23
- Claude cut a 2.6-hour video export to 20 minutes — but only after being told to rebuild the server — byhewar · 2026-10-23
- 3 flight-booking rules my AI agent checks that I'd never do by hand — Efistoffeles · 2026-10-23
- OpenJet claims Qwen3.8-27B coding runs 1.9x faster than llama.cpp on one RTX 3090 — JeremyCMorgan · 2026-10-23
- Building an autonomous SEO agent in Hermes with three skills: programmatic pages, Keywords Everywhere, DataForSEO — EXM7777 · 2026-10-23
- Building a sports betting AI agent with onchain execution and human approval by default: architecture and lessons — Dry-Comfortable-2678 · 2026-10-23