From the source
Vercel is launching Vercel CI in Beta on all plans, a continuous integration system that runs only the tasks affected by a code change instead of the whole workflow on every push.
- The company says the problem is that coding agents open more pull requests than ever, and most CI systems rerun everything even for a one-line change, so the more agents push, the longer teams wait.
- Vercel CI uses Turborepo to map tasks and their dependencies, reading turbo.json so existing Turborepo users have no separate CI config to write, and tasks are opted in with a "ci" tag.
- Tasks whose inputs have not changed come from cache, while the rest each run on their own machine on Hive, Vercel's compute layer, starting as soon as their dependencies finish.
- Vercel says its own CI is now 2-6x faster from git push to "CI passed" than before, and that Vercel CI has completed nearly 8 million tasks across its repositories and the private beta.
- Runs can be watched and inspected through the Vercel dashboard, Vercel CLI or Vercel MCP, and Vercel CI posts a check to
GitHub pull requests so existing branch protection rules can block merges on failure.
- As it works toward general availability, Vercel plans advanced observability, a vc ci CLI command for distributed execution before pushing code, and more granular test selection.
