avercel — Agent-Vercel: the Vercel CLI that fights back

The Problem

Trailing newlines are destroying your deploys

You pipe a secret into vercel env add. It silently appends \n. Your app breaks. Vercel shows no error. You question your career choices.

Terminal — oh no

# This looks fine...

echo "sk-abc123" | vercel env add SECRET_KEY production

✓ Added environment variable SECRET_KEY

# 45 minutes of debugging later...

vercel env pull .env

xxd .env | grep SECRET

0000: 534b 2d61 6263 3132 330a sk-abc123.

← that 0a is a trailing newline. your API key is broken.

The Fix

Drop-in replacement. Zero config.

avercel wraps the official Vercel CLI and patches the sharp edges. Same commands, no surprises.

❌ Before (vercel)

$ echo "sk-abc123" | vercel env add

# Silently stores "sk-abc123\n"

# App breaks in production

# No warning. No error.

# 🔥 Deploy breaks

# 🕐 45 min debugging

# 😤 Career crisis

✅ After (avercel)

$ echo "sk-abc123" | avercel env add

⚠ Stripped trailing whitespace from stdin

# Stores clean "sk-abc123"

# App works perfectly

# ✅ Deploy works

# ✅ Zero debugging

# ✅ Career saved

Features

Everything vercel should have been

Sensible defaults. Guard rails. Audit tools. All in a transparent wrapper.

🧹

Env Sanitization

Automatically strips trailing whitespace and newlines from piped stdin on env add. No more invisible characters breaking your secrets.

🔍

Env Check

Run avercel env check to audit all environment variables across all targets for trailing whitespace. Find the problems before they find you.

🚫

Disabled Commands

Block dangerous commands like deploy with custom error messages. Enforce CI/CD pipelines — no more cowboy deploys.

🛑

Blocked Environments

Block specific environment names with guidance messages. Prevent preview when your team uses dev.

⚡

Takeover Mode

Run avercel takeover to replace the global vercel command with avercel. One command — every vercel call now goes through avercel.

🤖

Agent-Ready

Bundled AgentSkill for AI coding agents. Your AI teammate knows how to use avercel out of the box. No hallucinated flags.

Get Started

Install in 10 seconds

avercel bundles Vercel CLI as a dependency — no separate install needed.

$ npm i -g avercel

Then just use avercel instead of vercel. All commands pass through. Or run avercel takeover to replace vercel globally.

Configuration

Optional, but powerful

Zero config by default. Add .avercel/avercel.yaml to your project when you need guardrails.

.avercel/avercel.yaml

# Block dangerous commands
disabled_commands:
  deploy: "Use CI/CD pipeline instead: git push origin main"
  promote: "Promotions are handled by the release workflow"

# Block wrong environment names
blocked_envs:
  preview: "This project uses 'dev', not 'preview'"
  staging: "We don't have a staging env. Use 'preview' or 'production'"