What problem does it solve?
Removes the need for interactive Vercel login by guiding users to deploy and manage projects using token-based authentication, reducing manual prompts and exposed secrets in command history.
Core Features & Use Cases
- Token discovery and safe usage: Locate VERCEL_TOKEN in the environment or .env and instruct users to export it rather than passing it on the command line.
- Project and team targeting: Explain when to use VERCEL_PROJECT_ID and VERCEL_ORG_ID, when to rely on .vercel metadata, and how to extract team slugs from project URLs.
- Deploy flows: Provide quick deploys when project IDs are available, full link-and-deploy flows when linking is required, and guidance for git-driven or CLI-triggered deployments.
- Environment variable management and inspection: Show non-interactive patterns for adding, listing, pulling, and removing env vars and emphasize using --format json for structured output.
- Working agreements & safety: Default to preview deployments, ask before pushing to git, never pass tokens as CLI flags, and avoid directly modifying .vercel files.
Quick Start
Deploy the current repository as a preview to Vercel using an exported VERCEL_TOKEN and optional VERCEL_PROJECT_ID without performing an interactive login.