Your AI agent asks so often, you stopped reading. Vercel's fix: ask less.
Your AI agent asks, and you click approve. Every time. It's in Vercel's own article: "Repeated prompts can turn that review into a habit of clicking approve." Anthropic counts 93% of Claude Code's prompts approved anyway. The obvious way out is a broad key, and in April an agent fixing staging found one in an unrelated file and deleted a company's production database, backups included, in nine seconds (the founder's account). Vercel's fix asks less: its agent reads production without asking, then asks once, with a plan. Approving it cuts a key for that plan, never more than your own access. Vercel admits the key is wider than the job, and a build log can trick the agent into using it. But past the key, the API says no. So let it look, read the one plan, approve once.
Source: "How Vercel Agent accesses production safely", Vercel Blog, Oct 23, 2026 (Tom Dale) https://vercel.com/blog/how-vercel-agent-accesses-production-safely Also: Anthropic Engineering, "How we built Claude Code auto mode" (Mar 25, 2026); Decrypt and DevOps.com on PocketOS (Apr 2026).
The stamp, the prompt cards, production draining, the key ring, the April room, the deployments, the build logs, the project grid and the gate are dramatizations; every quote and number on screen is from the sources.
When did you last actually read an approval prompt?
Transcript
Your AI agent asks so often, you stopped reading. You just click approve. It's in Vercel's own article. Repeated prompts can turn review into a habit of clicking approve. In Claude Code, 93% get approved. So, skip the prompts and hand it a master key. In April, an agent fixing staging found one and wiped a company's production database in 9 seconds. But Vercel's fix is to ask less. Looking needs no approval, so it investigates first. Then it asks once. One plan, what it'll change, and the access it needs. Approve, and it gets a key cut for that plan, never more than yours. But Vercel admits the key is wider than the job. Approve one redeploy, and it can reach other deployments, too. Trick it with a build log, and that key still works. But reach past the key, and the API says no. So, let it look, read the one plan, approve once. Because…
