Vercel CI enters beta with task tags for Turborepo

Teams can run CI for a Turborepo project with a single line of configuration: adding a tags entry such as "ci" to a task in turbo.json makes that task run in Vercel CI. Vercel CI runs each task marked with a ci tag on every push, and it only runs the CI affected by code changes.

According to Vercel, the service also handles task caching through Vercel Remote Cache, installs dependencies once per run, and caches dependencies across code updates.

Vercel says that in its internal repositories, the time from git push to a passing CI result is 2-6x shorter, which it links to CI keeping pace with coding agents. Developers can ask a coding agent to set up Vercel CI in a repository by running the vercel/ci setup skill, which selects initial tasks, configures Vercel CI and opens a pull request.

Agent-driven repositories that push often can add a ci tag to existing Turborepo tasks instead of writing separate CI pipeline configuration. Because only affected tasks run, pushes from coding agents should trigger less work.

Since the product is in beta, teams should check the documentation before relying on it for required merge checks.