The approval queue isn't a tax on your agents — it's the only part making them smarter
RobCatalanoGTM · reddit · 2026-11-02
Based on interviews with sales/marketing/RevOps leaders, the author splits agent deployments into two groups. Teams treating human approval as overhead to remove quickly suffered incidents (renewal pitches to churned customers, overwritten deal history) and shut down. Teams treating every approval/edit/rejection as their most valuable data ran a clear playbook: gate writes per action while reads stay free; require a one-line reason on every rejection — that's the training signal; graduate actions to auto when override rates stay low, pull them back on drift; and feed rejection reasons back into the agent's grounding context, not the prompt. A Gravitee 2026 report found only 14% of teams ship agents with full security/IT approval while 81% already have agents past planning, so most teams are in group one by default. The author discloses he runs a company in this space, but notes a spreadsheet of rejection reasons gets you most of the way.
More from coding & agent
- Overnight coding agents stall on questions: bidirectional answer routing is the missing piece — onitsoga · 2026-11-02
- Testing AI models via game-ready 3D assets: mix Blender with Tripo and Meshy — chongdashu · 2026-11-02
- Bivia by Articul8 skips the paragraph: a decision model that returns JSON with confidence and evidence — No-Asparagus-8011 · 2026-11-02
- dhh: agent era ends tech talent's immunity for being difficult, soft skills matter — bendee983 · 2026-11-02
- How to edit videos with Claude Code and Opus 5.5, plus 32 shared skills — aakashgupta · 2026-11-02
- Claude Code can edit video — the trick is dictating editor notes while recording — aakashgupta · 2026-11-02