Vercel CI is now in beta
By Steven Van ·
Vercel CI runs only the Turborepo tasks a change affects, is open to all plans, and cut push-to-pass time 2-6x in Vercel's own repositories.
Vercel CI is in beta on all plans. It runs CI for a Turborepo from a single line of configuration. Vercel says time from git push to "CI passed" is 2-6x shorter in its own internal repositories, which it ties to keeping up with coding agents that open more pull requests. Vercel CI has completed nearly 8 million tasks across Vercel's repositories and the private beta. Vercel describes it in its announcement.
How it works
Vercel CI reads turbo.json, so repositories already using Turborepo need no separate CI config. Repositories not yet on Turborepo need to add turbo.json and the turbo package. It also works in single-package repos. Adding "tags": ["ci"] to a task makes it run in Vercel CI, with no workflow YAML to maintain.
On each push, Vercel CI works out which tasks the change affects. Tasks whose inputs haven't changed come from cache, and Remote Cache is on by default. The remaining tasks each run on their own machine, on Hive, Vercel's compute layer, and start as soon as their dependencies finish. Each task gets the compute it needs and no more. Vercel CI also installs dependencies once per run and caches them across code updates.
Setup
Setup follows the documentation, or an agent can do it from the repository with this prompt: "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."
Inspecting runs
Runs can be watched through the Vercel dashboard, the Vercel CLI or Vercel MCP. The CLI commands include:
- vc ci ls lists CI runs for the repository
- vc ci inspect run lists tasks for a run
- vc ci logs run gets logs for all tasks in a run, and --task with --level=error narrows it to one task's stderr
- vc ci grep "WARNING" searches across run logs for a string
Vercel CI posts a check to the pull request on GitHub, so existing branch protection rules can block merges on failure.
Planned before general availability
- Advanced observability
- A vc ci CLI command for distributed execution before pushing code
- More granular test selection
