Introducing Vercel CI

AS

Anthony ShewVercel

·October 28, 2026

Coding agents are now opening pull requests at a rate no traditional CI pipeline was built for: every push triggers the full workflow, even when the change is a single line. Vercel CI, now in Beta, narrows each run to the tasks a change actually affects and provisions compute only for those checks — scaling in the same manner as Fluid compute does with traffic. On Vercel's own repositories, the push-to-"CI passed" interval is 2–6x faster than before.

Configuration comes from turbo.json

Vercel CI relies on Turborepo to map out tasks and their dependencies. It reads turbo.json, so teams already on Turborepo have no extra CI configuration to write. Teams that haven't adopted Turborepo can add turbo.json plus the turbo package; single-package repositories are supported as well. The next step is tagging the tasks Vercel CI should execute:

turbo.json

{
  "tasks": {
    "lint": {
      "tags": ["ci"]
    }
  }
}

That "tags": ["ci"] entry is the whole setup. There is no workflow YAML to maintain and no chance of the CI config drifting away from turbo.json, and Remote Cache is enabled by default.

Task execution

After a push from a developer or an agent, Vercel CI works out which tasks the change affects. Tasks whose inputs are unchanged are served from cache. Everything else runs on its own machine on Hive, Vercel's compute layer, with each task starting as soon as its dependencies complete.

Each task is provisioned the compute it requires and no more.

Adoption and day-to-day use

Setup is documented, and agents can be prompted from inside the repository to do it:

Set up Vercel CI for this repository. Run `npx skills use vercel/ci@setup` and follow the skill's instructions to select initial tasks, configure Vercel CI, and open a pull request.

Once running, CI can be watched and inspected through the Vercel dashboard, the Vercel CLI, or Vercel MCP. A failure leads directly to the failing task: you can see what is blocked behind it and open its logs, or search recent runs to check whether a test has been flaky all week.

Terminal

vc ci ls # List CI runs for the repository
vc ci inspect <run> # List tasks for a run
vc ci logs <run> # Get logs for all tasks in a run
vc ci logs <run> --task web#test --level=error # Get stderr for a specific task
vc ci grep "WARNING" # Search across run logs for a string

Vercel CI reports a check on the GitHub pull request, so existing branch protection rules can continue to block merges on failure.

Current status and roadmap

Vercel CI has completed close to 8 million tasks across Vercel's repositories and the private beta. Ahead of general availability, the planned additions are: