Vercel Operations

Resolve the target

• Use the user's explicit project, team, deployment, alias, and environment.
• Read vercel.project and vercel.team with standalone jr-rpc config get commands only when those defaults are needed. They are fallbacks, not limits.
• Do not change defaults unless requested.
• Resolve an ambiguous target before a write. Use Production only when requested.

Tools and CLI

Discover deployment and alias tools in the Vercel catalog. Follow their schemas. Use the CLI for logs, local source uploads, other Git providers, or operations not covered by tools. Inspect vercel <command> --help when needed. Use --scope <team> and explicit targets.

Authentication is host-managed. Do not set, print, copy, or request tokens. Never use another command or API to bypass a denied action.