Introducing Vercel CI
By Steven Van ·
The Beta runs only Turborepo tasks tagged "ci", with Remote Cache on by default, and currently supports GitHub repositories on Linux.
Vercel CI is now in Beta. It runs only the Vercel tasks affected by a code change, and each task gets its own compute. Vercel CI uses the Turborepo task graph to find the minimal set of tasks to run. Tasks that are unaffected or already cached are restored from cache or skipped. Vercel says time from git push to "CI passed" is 2-6x faster on its own CI than before.
How it works
On each git push, the following happens:
- Turborepo finds the tasks tagged "tags": ["ci"] in turbo.json.
- Vercel Remote Cache, which is on by default, is checked for tasks that are already cached.
- The remaining uncached, tagged tasks run in dependency order, each in its own compute instance on Hive, Vercel's compute layer.
- Task status is posted back to the source forge. If any task fails, Vercel CI is marked as failed.
There is no workflow YAML to maintain. Repositories already using Turborepo need no separate CI config. Others can add turbo.json and the turbo package, and single-package repos work too.
Setting it up
Vercel CI requires Turborepo 2.11.7 or later and Vercel CLI 64.3.1 or later. A coding agent can do the setup: the Vercel CI setup skill (npx skills use vercel/ci@setup) selects initial tasks, configures Vercel CI and opens a pull request.
To set it up manually, connect the GitHub repository to a Vercel project on your team, then run vercel ci enable from a local clone. Add the ci tag to each task that should run, for example the test task in turbo.json.
Finding runs and logs
CI runs appear in the CI tab of the dashboard, and pull requests link to the run from the GitHub merge box. Runs can also be inspected through the Vercel CLI, Vercel MCP and the OpenAPI specification. CLI commands include vc ci ls to list runs, vc ci inspect to list a run's tasks and vc ci logs to get task logs. Branch protection rules can block merging while Vercel CI is failing, the same way as with a GitHub Actions failure.
Limitations
- Linux is the only base image.
- GitHub is the only supported source forge.
- Pushing code to GitHub with git push is the only supported trigger.
- The repository must be connected to at least one Vercel project, and not to projects on multiple Vercel teams.
Vercel says features and configuration may change during the Beta.