Vercel CI enters beta, running only the Turborepo tasks a push affects

Vercel launched Vercel CI in beta, which reads turbo.json, skips unaffected or cached tasks and runs each remaining task on its own machine.

Vercel has put Vercel CI into beta on all plans, announced October 28, 2026. It uses your Turborepo task graph to run only the tasks a push affects. Unchanged tasks come from Remote Cache, and each remaining task runs on its own machine on Hive, Vercel's compute layer. The pitch is aimed at teams whose coding agents open PRs faster than CI can clear them. Vercel says push-to-"CI passed" time in its own repos is 2-6x faster. As AICoder notes, that is a vendor figure with no third-party or like-for-like comparison yet.

Setup is a tag, not workflow YAML. Add "tags": ["ci"] to a task in turbo.json. Alternatively, have your agent run npx skills use vercel/ci@setup. The docs require Turborepo 2.11.7+ and Vercel CLI 64.3.1+. Results post as a GitHub check, so branch protection works as before. Runs can be inspected via the dashboard, vc ci commands or Vercel MCP.

The current limits matter more than the speed claim:

Vercel's migration guide says to keep macOS or Windows jobs in GitHub Actions. One early reader's suggestion is to start small and tag only type checks and tests. Lock-in to Vercel's compute and cache isn't addressed in the sources.

Sources