Skip to content

CI that keeps up with your agents

Install dependencies once per run. Run independent tasks in parallel. Reuse cached results with Turborepo.

Set up Vercel CI
Three illustrative pushes to main: a shared UI change executes 4 tasks and restores 3 from cache; a docs-only change restores all 7; an app change executes 3 and restores 4. Each run installs dependencies once. Independent tasks run in parallel; the storefront test task waits for the storefront build task. Shared UI is an input to app builds and tests. README is excluded from task inputs. Timings are illustrative.
  1. ~/storefront main

Faster feedback, proven at scale

  • 9×

    Faster from push to passed

    Measured in Vercel’s repositories at launch

  • 8M

    Tasks completed

    Across Vercel's repositories

Run the work your change needs

Your task graph defines the work and its dependencies. Vercel CI shares setup across tasks and runs independent tasks in parallel on isolated compute.
Built on Turborepo

Your task graph is your CI configuration

Use the same Turborepo tasks locally and in CI. Keep tasks and dependencies in turbo.json and tag the checks you want to run. Enable Vercel CI for your GitHub repository and push your changes. Your task graph defines what runs and what it depends on. No separate workflow YAML to maintain.
Configure your tasks
turbo.json
{
  "tasks": {
    "build": {},
    "lint": {
      "tags": ["ci"]
    },
    "test": {
      "dependsOn": ["build"],
      "tags": ["ci"]
    }
  }
}
Dashboard, CLI, and MCP

Give your agent context to keep moving

Inspect runs, read task logs, and investigate failures through Vercel MCP and CLI. Review the same runs in your dashboard. Find the failing task, see its dependencies, and search logs across recent runs. Your agent can use that context for its next fix.
Explore the CLI
Terminal
# Find your latest runs
vc ci ls
# Inspect tasks and dependencies
vc ci inspect <run>
# Read errors from a failing task
vc ci logs <run> --task web#test --level=error
# Search across run logs
vc ci grep "WARNING"

Before your first run

Do I need Turborepo?
Yes. Vercel CI uses your Turborepo task graph and requires Turborepo 2.11.7 or later. It works with monorepos and single-package repositories. You’ll also need Vercel CLI 64.3.1 or later.
Which repositories are supported?
The beta supports private GitHub repositories. Public repositories and other Git providers are not currently supported. See current limitations.
Do I need to host on Vercel?
No. You can use Vercel CI without deploying to Vercel or linking a Vercel project. Install the Vercel GitHub App, link your GitHub account to Vercel, and enable CI from the Vercel CLI.
What starts a CI run?
A git push to GitHub starts a run. Vercel CI checks your tagged tasks and their dependencies, restores cached results, and executes the remaining work. Linux is currently the supported execution environment.
Can I migrate checks from GitHub Actions?
Yes. Move your tasks and secrets, compare the pipelines, and then switch your required status checks. Start with the Vercel CI documentation.
Can Vercel CI block a pull request from merging?
Yes. Vercel CI reports a check to GitHub. Add it to your branch protection rules to prevent merges when CI fails.
Is Vercel CI generally available?
Vercel CI is in public beta. Features and configuration may change. Check the documentation for current requirements and the pricing page for usage details.

Put your next push on Vercel CI

Set up Vercel CI