# Vercel — Introducing Vercel CI

- Company: Vercel (vercel.com)
- Announced: 2026-10-28T07:00:00+00:00
- Category: developer-tool-release
- Coverage: not counted
- Announcement: yes
- Group: announcements
- Source: https://vercel.com/blog/introducing-vercel-ci
- Record: https://forck.live/items/28952-introducing-vercel-ci
- Subject: v0 / AI SDK / AI Gateway

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.

## Evidence

Verbatim from https://vercel.com/blog/introducing-vercel-ci:

> Coding agents are opening more pull requests than ever, and each one waits on CI before anyone can review or merge it. Most CI systems run the entire workflow on every push, even a one-line change. The more your agents push, the more time you spend waiting on CI.
> 
> Today, we're announcing Vercel CI in Beta. It runs only the tasks affected by your code change, and spins up only the compute those checks need, the same way Fluid compute scales with your traffic.
> 
> At Vercel, our CI now keeps up with our coding agents. Time from git push to "CI passed" is 2-6x faster than it was before.
> 
> Copy link to heading How it works
> 
> Vercel CI uses Turborepo to understand your tasks and which ones depend on each other. It reads turbo.json , so if you're already using Turborepo, there's no separate CI config to write.
> 
> If you're not on Turborepo yet, add turbo.json and the turbo package. It works in single-package repos too.
> 
> Then tag the tasks you want Vercel CI to run.
> 
> { "tasks" : { "lint" : { "tags" : [ "ci" ] } } }
> 
> "tags": ["ci"] is all you need to get started. No workflow YAML to maintain, no drift between your CI config and turbo.json , and Remote Cache is on by default.

---

Record: https://forck.live/items/28952-introducing-vercel-ci
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md