When a guardrail is hit that often, it stops being a check and starts being a formality. This is the ‘consent fatigue’ trap. Just like the reflexive clicking of cookie banners, frequent manual approval prompts train users to prioritize flow over scrutiny. The danger isn’t that agents lack capability. They have more agency than our UX models can safely contain. We are currently treating contextual judgment calls, like ‘Should the agent run this specific shell command now?’, as binary authorization. This creates a dangerous situation where the user becomes a rubber stamp for potentially overeager behavior, like accidental data exfiltration or scope creep. And technically, nothing goes wrong, because hey, the user has approved the action! Agentic UX should not be endless manual confirmation. And definitely not automated confirmations. It’s a shift toward risk-tiered automation: Safe-tool allowlists for routine tasks. Context-aware classification for high-risk actions. Hard stops for genuinely dangerous operations. We need to move from asking ‘Can the agent do this?’ to ‘Is this specific action safe in this specific context?’ What percentage of your current safety checkpoints are actually conscious reviews, and what percentage are just friction that your team has learned to blindly ignore? submitted by /u/Familiar_Flow4418
Originally posted by u/Familiar_Flow4418 on r/ClaudeCode