Vercel Ecosystem

Vercel is the default hosted web-app and AI-app ecosystem route when the task involves Next.js deployment, Vercel AI SDK, project env vars, preview URLs, or Vercel-managed runtime behavior. Source: Ecosystem Capability Coverage, 2026-06-27; Skill Resolver, 2026-06-27

When To Use This

Use Vercel when the work is about preview deployments, production deployment, domains, environment variables, Next.js runtime behavior, Vercel AI SDK, Vercel Sandbox, or Vercel observability. Use local project docs first for exact Next.js version behavior. Source: Skill Resolver, 2026-06-27

Decision Matrix

Core Model

Vercel has three different layers that should not be collapsed: hosting/control-plane operations, Next.js framework behavior, and AI/runtime libraries. Platform operations use MCP or CLI. Framework facts come from the installed project. AI features route through Vercel AI SDK and model gateway pages. Source: Skill Resolver, 2026-06-27

Secret Rotation

Treat "rotate everything in Vercel" social posts as incident-response prompts, not as proof of a platform breach. The durable checklist is still useful: rotate Vercel environment variables, regenerate connected GitHub/integration tokens when the integration boundary is in scope, inspect builds/logs/artifacts for copied secrets, revoke affected Stripe/database/API keys at the provider, then redeploy every dependent production and preview project before invalidating the old credential. Vercel's docs explicitly say env-var changes apply only to new deployments, team-level variables require redeploying every linked project, and integrations may have their own Rotate Secrets flow. Source: X/@buildwithhassan, 2026-04-19; Source: Vercel rotating environment variables docs, checked 2026-07-04; Source: Vercel environment variables docs, checked 2026-07-04

For CLI work, prefer vercel env run -- <command> when a tool can consume variables without writing them to a local file. Vercel's CLI docs warn that piping secrets with echo can save values in shell history, and production/preview variables default to sensitive where supported. That makes rotation an order-of-operations problem: generate the replacement credential at the source provider, update Vercel, redeploy, verify, then revoke the old credential. Source: Vercel CLI env docs, checked 2026-07-04

WebSockets Public Beta

As of the 2026-06-22 public beta, Vercel Functions can serve WebSocket connections for realtime features such as interactive AI streaming, chat, and collaborative apps. Connections run on Fluid Compute, use standard Node.js libraries such as ws, and higher-level libraries such as Socket.IO are supported. Vercel's docs note that a single WebSocket connection is pinned to one Function instance for its lifetime, while Fluid Compute allows one instance to handle multiple WebSocket connections. Pricing follows the Functions/Fluid Compute model, with Active CPU billing charging processing time rather than idle connection time. Source: Vercel changelog, 2026-06-22; Source: Vercel WebSockets docs, 2026-07-04

Use this when a Vercel-hosted app needs bidirectional runtime state on the same deployment surface. Keep SSE as the simpler default for one-way LLM text streams; use WebSockets when clients send live audio, tools, collaboration events, or agent-control messages back to the server.

Long-Running Functions

As of the 2026-06-15 changelog, Vercel Functions using the Node.js and Python runtimes can run up to 30 minutes for Pro and Enterprise teams. Durations above the generally available 800-second limit are still beta, require Fluid Compute, and must be configured per function with maxDuration = 1800 or equivalent vercel.json function config. Source: Vercel changelog, 2026-06-15; Source: Vercel duration docs, checked 2026-07-04

This matters for AI apps because the named use cases are long LLM reasoning/tool calls, multi-minute streamed responses, document/media processing, OCR/extraction, web scraping/browser automation, and complex Workflow or Queue handlers. Active CPU billing applies while code executes and pauses while a Function waits on I/O, but Vercel Workflows is still the better route when work must pause/resume for minutes to months rather than merely run longer inside one invocation. Source: Vercel docs, checked 2026-07-04

Vercel Flags

As of the 2026-04-16 GA changelog, Vercel Flags is a platform-native feature-flag provider for Vercel projects and is available on all plans. The useful model is "deploy is not release": merge code continuously, then release with targeting rules, reusable segments, progressive rollout, or a kill switch. Values can be boolean, string, number, or JSON, and Vercel's provider uses active global replication so flag configuration can propagate globally without adding a new flag service to the app stack. Source: Vercel Flags GA changelog, 2026-04-16; Source: Vercel Flags docs, checked 2026-07-04

The implementation route is server-first and framework-native. The open-source flags package is current at 4.2.0, @flags-sdk/vercel is current at 1.4.3, and the vercel CLI is current at 54.20.1 as of the 2026-07-04 npm check. Use flags/next or flags/sveltekit for framework adapters, @flags-sdk/vercel for Vercel as the provider, and OpenFeature when another provider must remain the decision backend. The Vercel blog frames the major advantage as server-side evaluation: no client-side flag round trip, flicker, or layout shift before the correct variant renders. Source: Vercel blog, 2026-06-22; Source: npm registry via npm view, 2026-07-04

Agent-operable surfaces matter here: the dashboard sits alongside deployments, automatic registration turns code-defined flags into dashboard drafts, precompute can keep static variants on the CDN, Flags Explorer lets a browser session override values without changing shared config, and vercel flags exposes the same lifecycle from the terminal. This makes Vercel Flags a good fit for AI-app rollouts, model-routing experiments, beta gates, and operational kill switches when the app already deploys to Vercel.

Services, Agent Runs, and CLI Discipline (Jul 2026)

The July Ship cluster expands Vercel from "one Next app" toward a multi-service project shape. Dockerfile support lets non-Node services run on Vercel with a Dockerfile.vercel; Vercel Services groups multiple frameworks/services under one project with atomic deployment/rollback, one preview URL, and private service-to-service networking. Treat this as a platform route for cohesive full-stack apps, not a blanket reason to migrate every microservice. Source: X/@vercel, 2026-07-01; Source: X/@vercel, 2026-07-01; Source: X/@vercel, 2026-07-01

For agents, the higher-signal changes are feedback surfaces. vc deploy --dry gives agents and humans a deployment preview before creating a real deployment, and vc agent-runs plus Vercel MCP exposes Agent Runs traces to coding agents. That makes a Vercel-hosted agent loop more inspectable: an agent can read prior run traces, inspect deployment consequences, and iterate before pushing production state. Source: X/@vercel_dev, 2026-07-02; Source: X/@vercel_dev, 2026-07-04

konsistent is the structural-convention linter from Vercel Labs. Current package authority on 2026-07-06 is konsistent@1.0.0-beta.2, Apache-2.0, modified 2026-07-06; repo HEAD is c99814601b62e507bd20af12368ea931232421a5, with package tags through konsistent@1.0.0-beta.2. Route it near Frontend and Design Skills and Vercel AI SDK work when TypeScript APIs need agent-enforced conventions. It is not a style formatter; it is a convention checker for project structure and API consistency. Source: X/@vercel, 2026-07-02; Source: npm/GitHub, 2026-07-06

The Vercel CLI copywriting-guidelines PR is a small but important agent-facing signal: command output, errors, and help text are part of the harness. If agents are going to call CLIs and recover from failures, CLI copy should be specific, action-oriented, and machine-readable enough for retry logic. Route repeated CLI-authoring work through Security and Review Skills and Agent Legibility. Source: GitHub vercel/vercel PR 16774 via X/@rauchg, 2026-07-04

Vercel Agent Skills Import

Vercel Agent Skills is the local audit map for vercel-labs/agent-skills at commit f8a72b9603728bb92a217a879b7e62e43ad76c81. The repo's nine skills are useful, but Kevin's stack already has owners for most of them:

The deploy/token working agreement is now part of the Vercel route: use VERCEL_TOKEN from the environment instead of --token, read .vercel/project.json or .vercel/repo.json only for state discovery, default to preview deployments, use --format json where agents need structured output, inspect deployments with vercel inspect, and never push git or deploy production unless Kevin asked for that exact mutation. Source: vercel-labs/agent-skills deploy-to-vercel, vercel-cli-with-tokens, and vercel-optimize, checked 2026-07-06

Routing Summary

Preferred order: Vercel MCP for account/project inspection, vercel CLI for local/dev/deploy/env operations, project-local Next docs for framework facts, then Vercel-specific skills for repeatable procedures. Source: Skill Resolver, 2026-06-27

Failure Modes

• Treating generic Next.js advice as version-matched local truth.
• Deploying without confirming project, team, env, and target branch.
• Mixing AI SDK application bugs with Vercel platform bugs.
• Editing generated packs instead of the underlying wiki or skill page.

Verification Path

Run vercel whoami or a read-only MCP lookup before mutations. For deploy work, capture preview URL, deployment state, env assumptions, and rollback path. For framework work, run the project build or the smallest honest Next.js check. Source: Skill Resolver, 2026-06-27; config/capability-harvest-seeds.json

---

Timeline

• 2026-07-06 | Absorbed the July Vercel Ship cluster: Dockerfile-on-Vercel, Vercel Services/multiple frameworks in one project, vc deploy --dry, Agent Runs in MCP/CLI, konsistent@1.0.0-beta.2, and CLI copywriting guidelines. Local route: Services/Dockerfile change platform fit; dry-run deploy and Agent Runs improve agent feedback; konsistent is a candidate structural-convention checker for TypeScript agent-maintained codebases. Source: X/Vercel bookmarks and npm/GitHub source checks, 2026-07-06
• 2026-07-06 | Reviewed every public skill in vercel-labs/agent-skills at commit f8a72b9603728bb92a217a879b7e62e43ad76c81 and routed them through local owners rather than adding duplicate executables. Imported the deploy/token working agreement and parked vercel-optimize as metric-backed only. Source: GitHub vercel-labs/agent-skills, 2026-07-06
• 2026-07-04 | Source-reviewed the 30-minute Vercel Functions bookmark. Added long-running Functions as a Fluid Compute capability: Node/Python Pro and Enterprise Functions can opt into 1800-second maxDuration; durations above 800 seconds are beta and per-function; Workflows remains the route for unbounded pause/resume. Source: X/@vercel_dev, 2026-06-15; Source: Vercel changelog/docs, checked 2026-07-04
• 2026-07-04 | Added Vercel secret rotation as an incident-response path: social panic posts should not be treated as breach evidence, but the operational checklist is real when paired with official docs: update env vars, redeploy all dependent projects, rotate integrations/provider-side credentials, avoid shell-history leaks, and revoke old secrets only after verification. Source: X/@buildwithhassan, 2026-04-19; Source: Vercel env docs, checked 2026-07-04
• 2026-07-04 | Deep-reviewed the Vercel Flags bookmark and refreshed the canonical Vercel page plus vercel-flags skill from beta-era notes to GA/current-docs status: GA 2026-04-16, all plans, server-first Flags SDK, dashboard drafts, Flags Explorer, precompute, CLI lifecycle, and npm versions flags@4.2.0, @flags-sdk/vercel@1.4.3, vercel@54.20.1. Source: X/@vercel, 2026-06-22; Source: Vercel blog/docs/changelog/CLI, checked 2026-07-04
• 2026-07-04 | Deep-reviewed the Vercel WebSockets public beta bookmark. Added WebSockets as a Vercel Functions/Fluid Compute capability, with ws/Socket.IO support, connection pinning semantics, and Active CPU pricing nuance. Source: X/@vercel_dev, 2026-06-22; Source: Vercel changelog and docs, 2026-07-04
• 2026-06-27 | Canonical ecosystem page created so packs and routing distinguish Vercel platform operations from Next.js framework facts and Vercel AI SDK application work. Source: User request, 2026-06-27; Ecosystem Capability Coverage