CLI Workflows
Last updated March 2, 2026
These workflows show how to compose multiple Vercel CLI commands into complete work sessions. Each workflow walks through a real task from start to finish, including the reasoning between steps.
Workflows are distributed throughout the docs, colocated with the features they use. This page links to all available workflows.
| Workflow | Description | Entry point |
|---|---|---|
| Debugging production 500 errors | Find, fix, and verify production 500 errors using logs, inspect, and preview deployments | Observability |
| Rolling back a production deployment | Recover from a bad production deployment with rollback, investigation, and redeployment | Deployments |
| Debugging slow Vercel Functions | Diagnose and fix slow functions using timing analysis, logs, and configuration tuning | Functions |
| Diagnosing and fixing cache issues | Identify and fix stale CDN cache, data cache, and build cache problems | CDN Cache |
| Workflow | Description | Entry point |
|---|---|---|
| Deploying a project from the CLI | Set up and deploy a project end-to-end, from linking to production with a custom domain | Projects |
| Setting up a custom domain | Add a custom domain, configure DNS records, and verify SSL certificates | Domains |
| Managing environment variables across environments | Add, sync, and verify environment variables across development, preview, and production | Environment Variables |
| Promoting a preview deployment to production | Test a preview deployment and promote it to production without rebuilding | Deployments |
| Performing a rolling release deployment | Gradually roll out a production deployment with traffic stages and monitoring | Rolling Releases |
| Workflow | Description | Entry point |
|---|---|---|
| Managing redirects at scale | Add, bulk upload, version, and roll back project-level redirects | Redirects |
| Managing Vercel Blob storage from the CLI | Create blob stores, upload files, organize content, and manage storage | Vercel Blob |
| Workflow | Description | Entry point |
|---|---|---|
| Running commands in a Vercel Sandbox | Create isolated sandbox environments to run builds, tests, and commands safely | Vercel Sandbox |
| Workflow | Description | Entry point |
|---|---|---|
| Rolling out a new feature | Create a feature flag, wire it into your app, and progressively enable it across environments | Vercel Flags |
| Running an A/B test | Set up an A/B test, track results through Web Analytics, and clean up afterward | Vercel Flags |
| Cleaning up after a full rollout | Audit active flags, remove a fully rolled-out flag from code, and archive it | Vercel Flags |
| Setting up Flags Explorer | Add Flags Explorer to the Vercel Toolbar so you can override flag values on preview deployments | Vercel Flags |
These guides help you delegate code-generation tasks to a coding agent like Claude Code, Cursor, or Cline. Each one provides prompts you can copy into your agent to scaffold a full integration.
| Guide | Description | Entry point |
|---|---|---|
| AI Gateway agent quickstart | Set up AI Gateway with the AI SDK using prompts and cURL verification | AI Gateway |
| Sign in with Vercel agent quickstart | Scaffold the full OAuth flow with PKCE, token handling, and a profile page | Sign in with Vercel |
| Routing Middleware agent quickstart | Create routing middleware for redirects, auth checks, or geolocation rewrites | Routing Middleware |
These workflows are designed as composition patterns. Each one shows a complete sequence of CLI commands with the reasoning that connects them. AI coding agents can use these patterns to:
- Learn when to reach for each Vercel CLI command
- Understand the investigation flow for common problems
- Compose commands into multi-step sessions for novel situations
- Follow the same debugging methodology that experienced Vercel users follow
Was this helpful?