Vercel launches Vercel CI in beta for agent-driven pull requests

Vercel CI runs only the tasks affected by a code change and starts only the compute those checks need. Vercel says its own CI now keeps up with its coding agents, with time from git push to a passing run 2 to 6 times faster than before.

Vercel CI uses Turborepo to read task dependencies from turbo.json, so Turborepo users need no separate CI configuration. Teams tag the tasks they want CI to run, such as a lint task tagged ci, and tasks with unchanged inputs are served from cache. The remaining tasks run on their own machines, powered by Hive, Vercel's compute layer, and Remote Cache is on by default.

Vercel CI posts a check to GitHub pull requests, so existing branch protection rules still apply. Runs can be inspected in the Vercel dashboard, with the Vercel CLI, or through Vercel MCP, including commands that fetch task logs and search across runs. Vercel says it has completed nearly 8 million tasks and plans advanced observability, distributed execution before pushing, and more granular test selection before general availability.

Agent-generated pull requests can get CI results without a hand-maintained workflow file, provided the repository uses Turborepo and the tasks are tagged. Because results appear as GitHub checks, agents can pull failing task logs through the CLI or MCP instead of waiting for a person to open the dashboard. Since the product is in Beta, its commands and behavior may change before general availability.