vercel-deploy

Topics in the source

• Vercel Deploy
• Prerequisites
• Quick Start
• Fallback (No Auth)
• Production Deploys
• Output
• Troubleshooting
• Escalated Network Access

Deploy any project to Vercel instantly. Always deploy as preview (not production) unless the user explicitly asks for production. When sandboxing blocks the deployment network calls, rerun with sandboxpermissions=requireescalated. The deployment might take a few minutes. Use appropriate timeout values. Just run this (with a 10 minute timeout): Important: Use a 10 minute (600000ms) timeout for the deploy command since builds can take a while. If that fails with "No existing credentials found", use the fallback method below. If CLI fails with auth error, use the deploy script: The script handles framework detection, packaging, and deployment. It waits for the build to complete and returns JSON with previewUrl and claimUrl. Tell the user: "Your deployment is ready at [previewUrl]. Claim it at [claimUrl] to manage your deployment." Only if user explicitly asks: Show the user the deployment URL. For fallback deployments, also show the claim URL. Do not curl or fetch the deployed URL to verify it works. Just return the link. If deployment fails due to network issues (timeouts, DNS errors, connection resets), rerun the deploy with escalated permissions (use sandboxpermissions=requireescal

This is an excerpt. Refer to the complete source and its current requirements.