Vercel Logs

Safety

1. Read-only. NEVER run vercel deploy, vercel rollback, vercel alias, vercel env add/rm, vercel project rm, or any mutation. This skill only reads logs.
2. NEVER print secrets from log output. If a log line contains env var values, API keys, or tokens, redact before presenting.
3. Use --no-branch always. The CLI auto-detects the local git branch and silently filters to it — wrong for production debugging. Always pass --no-branch or --environment production explicitly.
4. Detach stdin. Append < /dev/null to every vercel command. Without it the CLI sniffs the TTY and hangs in agent shells.
5. Bound output. Always pass --limit N (default 20, max 100). For --follow runs, cap the observation window and kill the terminal when done — do not follow indefinitely.

Prerequisites