Vercel CI: OP next to GitHub Actions, Mid as a full replacement

Verdict, October 29, 2026. OP beside GitHub Actions, for Linux checks you can express as Turborepo tasks, on a GitHub repo that already connects to one Vercel team. Mid as the only pipeline. Mid on Hobby: the beta is offered on all plans, and the pricing page prints no Hobby rate. The 2 to 6 times figure is Vercel's, from its own repos. No letter moves on the AI Coding Agents board. Cursor, Claude, and Codex stay where the October 15 list put them. OP or Mid has not enabled Vercel CI and has not timed a run.

Pages below were read October 29, 2026.

What opened on October 28

NEW On October 28, 2026, Vercel announced Vercel CI in beta. It reads turbo.json, takes tasks tagged ci, skips tasks the change does not affect, and restores cached tasks from Vercel Remote Cache, which is on by default. A single-package repo can add turbo.json and the turbo package. A finished run posts a GitHub check, so existing branch protection can block the merge. The trigger is git push. The changelog's "runs on every push" is that trigger. Execution is the affected, uncached subset. Sources: blog (opens in a new tab), changelog (opens in a new tab), docs (opens in a new tab).

VENDOR CLAIM The blog says time from git push to "CI passed" is 2 to 6 times faster than before, at Vercel. The changelog says the wait in Vercel's internal repositories is 2 to 6 times shorter. The blog also says nearly 8 million tasks have completed across Vercel's repositories and the private beta. The posts name no repos, no old pipeline, and no timing method.

Docs require Turborepo 2.11.7 or later and Vercel CLI 64.3.1 or later. Older Turborepo rejects a task-level tags key with Found an unknown key. Connect the GitHub repo to a Vercel project, then run vercel ci enable from a local clone. Enable before the push that carries the tags. A push made earlier does not produce a run. The agent path is a prompt that runs npx skills use vercel/ci@setup and opens a pull request. Sources: docs (opens in a new tab), migration guide (opens in a new tab).

UPDATE CLI 64.3.1 or later inspects runs with vercel ci ls, inspect, logs, grep, and rerun. inspect --wait waits up to 10 minutes and exits 1 on failure. The migration guide names MCP tools for the same job: list_vercel_ci_invocations, get_vercel_ci_invocation_tree, get_vercel_ci_task_logs, and retry_vercel_ci_invocation. The launch post prints those inspection commands as vc ci. Its general-availability list is separate: advanced observability, a vc ci command for distributed execution before you push, and more granular test selection. Sources: CLI (opens in a new tab), migration guide (opens in a new tab), blog (opens in a new tab).

The bill

PRICE A CPU minute is one CPU running for one minute, the same unit as Builds. Pro is $0.0035 per CPU minute. Enterprise is Custom. Vercel's example is a task with 8 CPUs that runs for 2 minutes and 30 seconds: 8 times 2.5 is 20 CPU minutes. At the Pro rate, 20 times $0.0035 is $0.07. That last step is arithmetic on the published price. Time rounds up to the next second, with a minimum of 1 second. Source: CI pricing (opens in a new tab).

PRICE Each run bills bootstrapping, 4 CPUs by default, and each task that actually runs, 2 CPUs by default. A task restored from cache, or skipped because the change does not affect it, adds no task minutes. Memory is 2 GB per CPU, so the default task is 4 GB and an 8 GB task needs ci:cpus:4, which is twice the CPU minutes of the default for the same wall clock. The cap is 32 CPUs and 64 GB. The install step can be set from 1 to 32 CPUs under ci.bootstrapping.resources.vcpus in vercel.json. An invalid value makes Vercel ignore the ci configuration. Sources: CI pricing (opens in a new tab), configuration (opens in a new tab).

NERF The pricing table names Pro and Enterprise. It has no Hobby row and no included allowance. The launch post says the beta is available on all plans. That sentence is availability. The rate table is the bill. Source: blog (opens in a new tab), CI pricing (opens in a new tab).

What stays in GitHub Actions

NERF The docs limit the beta to a Linux image, GitHub, and git push. The repo must connect to at least one Vercel project, and it must not connect to projects on more than one team. Features and configuration may change. The enable error for the team limit is It's connected to projects on more than one team. Sources: docs (opens in a new tab), migration guide (opens in a new tab).

NERF Task images are Amazon Linux 2023 by default and Ubuntu 24.04 with ci:os:ubuntu. Both are x86_64 and ship Node.js 24.18.0. Installs stay on Amazon Linux even when the task uses Ubuntu. Ubuntu's Node row lists corepack. Amazon Linux's lists npm and npx. The migration guide's sample Actions workflow is Node 22 on Ubuntu, and it says to confirm the image before a task moves. macOS, Windows, deploys, publishes, schedules, and issue or label jobs stay in GitHub Actions, as does any command that is not yet a Turborepo task. A pull_request workflow tests GitHub's merge commit. Vercel CI tests the pushed commit, so two green checks can be two trees. Remote Cache replaces TURBO_TOKEN and TURBO_TEAM for moved tasks. Keep those secrets if Actions still reads them. Sources: images (opens in a new tab), migration guide (opens in a new tab).

Who should turn it on

BUFF OP next to Actions when the forge is GitHub, the repo is on exactly one Vercel team, the checks are Linux lint, typecheck, or unit tests, and agents such as Cursor, Claude, or Codex open enough pull requests that a full workflow on every push is the wait. Tag the no-secret tasks. Leave Actions required. Pro is the plan with a printed rate. The guide's cutover is several matching pull requests, then a required Vercel CI check, then deletion of only the Actions checks that moved.

NERF Mid on Hobby, on another forge, on two Vercel teams, or for log access alone. Hobby has no printed CI price. GitLab and Bitbucket are outside the forge list. A second team blocks enable. vercel ci logs and the MCP tools read a run that already exists. They do not move a job.

The board stays on October 15

Vercel CI runs tasks. It is not a coding agent, so the October 15 AI Coding Agents list does not gain a row and does not change a letter. S stays locked. The agents that open the pull requests stay in the tiers that page already states.

What to do today

On GitHub, with one Vercel team, run vercel ci enable, tag lint, typecheck, and unit test with ci, and read both checks. Leave Actions required until several pull requests match.
Keep macOS, Windows, scheduled, deploy, and publish jobs in Actions. On Pro, price bootstrap CPUs plus CPUs on tasks that ran. An 8 GB task is ci:cpus:4.
On Hobby, watch the invoice. The pricing page prints no Hobby rate and no included allowance.

The weekly patch is on beehiiv: subscribe free (opens in a new tab).

The OP or Mid Team

Sources

Checked October 29, 2026.