Unverified50% confidenceEventExact time
Vercel initially maintained a separate permission list for the Agent, which could fall out of sync with the OAuth service that issues tokens, and later the two were unified under the same set of scope definitions.
1
Sources
50%
Confidence
Long-term
Relevance
10/23/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedVercel Agent's credentials differ by type of work: read-only investigation uses the read-only baseline token; approved Vercel changes add extra scopes; external actions (such as opening a GitHub PR) use the corresponding provider's own credentials and permissions.72% similarUnverifiedVercel Agent's permissions are defined by scopes (capability names recognized by the authorization system), and any plan that exceeds the read-only baseline (all registered scopes beginning with `read:`) requires overall approval.68% similarUnverifiedVercel Connect enables scoped connectors and mints tokens for each agent task, so that agents only access the specific context needed for their work.67% similarUnverifiedVercel's Agent Skill concept is consistent with the Agent Skills concept proposed by Anthropic and OpenAI's function calling schema approach, all of which let tools actively adapt to Agents.67% similarUnverifiedVercel Agent adopts a plan-driven permission model: first investigate the problem, then propose a plan containing specific operations and required permissions, and the user approving the plan grants the permissions needed for execution.66% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1090319API
curl https://kongchang.com/api/v1/knowledge/claims/1090319MCP
get_claim(id=1090319)