Vercel Agent asks for a plan before touching production: one approval unlocks scoped access beyond a read-only baseline
When Vercel Agent works on a production problem, it investigates automatically under read-only access, then proposes a plan listing the tasks it would do and the permissions they need, and only after the user approves that plan does it receive access beyond the read-only baseline. Access is defined by scopes, the named capabilities recognized by Vercel's authorization system; a plan requesting more than the baseline, or including supported external actions, waits for approval as a whole, and the runtime checks the plan is active before selecting its approved credential while Vercel APIs check each request against that credential's permissions.