Scope Registry
The single source of truth for the permission system, centrally managing all available scope definitions and their metadata (name, description, associated resource types). It is used for plan validation, approval and token preparation.
Timeline (last 90 days)
When a session is established, Vercel Agent loads the definitions from the scope registry into an in-memory catalog and uses it in three stages: plan validation, approval and token preparation.
If a task requests an outdated scope, the Vercel Agent system rejects the plan and returns the valid scopes, requiring the Agent to explicitly correct it rather than falling back to broader permissions.
Vercel Agent caches the scope registry catalog and validates stored plans against the cached copy when loading them; before the catalog refreshes, checks reflect the cached definitions, which is a time window the team accepted in the trade-off.
All Facts (3)
When a session is established, Vercel Agent loads the definitions from the scope registry into an in-memory catalog and uses it in three stages: plan validation, approval and token preparation.
50%UnverifiedIf a task requests an outdated scope, the Vercel Agent system rejects the plan and returns the valid scopes, requiring the Agent to explicitly correct it rather than falling back to broader permissions.
50%UnverifiedVercel Agent caches the scope registry catalog and validates stored plans against the cached copy when loading them; before the catalog refreshes, checks reflect the cached definitions, which is a time window the team accepted in the trade-off.
50%