Vercel aligns agent permission checks with its token service

Vercel says it moved Vercel Agent to the same permission definitions used by its OAuth service, replacing a separate list that could fall out of sync. The change lets the system reject unknown or malformed permissions before presenting a production change for approval. The agent investigates with read-only access, then requests additional permissions through a plan. Vercel APIs enforce the resulting token's permissions on each request, and approving a plan cannot grant authority beyond the user's existing access. Those permissions can still exceed the specific task: deployment write access does not restrict a token to the single deployment named in a plan.