ToolDev ToolsInfrastructureciagentsperformance
Vercel CI
Vercel's CI service, in beta on all plans. It reads your turbo.json, runs only the tasks a change affects, gives each task its own machine and serves unchanged ones from Remote Cache.
Added November 4, 2026Published October 28, 2026
The pitch is aimed at agent-heavy repos: coding agents open more PRs than ever, and most CI systems rerun the whole workflow on every push. Vercel CI uses Turborepo's task graph instead. There's no workflow YAML; you tag tasks in turbo.json with "tags": ["ci"], and it works in single-package repos too. Tasks whose inputs haven't changed come from Remote Cache, which is on by default, and the rest each run on their own machine on Hive, Vercel's compute layer, starting as soon as their dependencies finish. Vercel reports 2-6x faster push-to-green on its own repositories.
It posts a GitHub check, so existing branch protection keeps working. Runs can be inspected from the dashboard, the Vercel MCP server or the CLI (vc ci ls, vc ci inspect, vc ci logs --task web#test --level=error, vc ci grep), and setup is itself an agent skill: npx skills use vercel/ci@setup. Launch post.
Related
- AlchemyInfrastructure as Effects. Cloud resources and the application code that uses them live in one type-safe Effect program in TypeScript, across Cloudflare, AWS, GCP, Kubernetes, Fly, Neon, PlanetScale, Stripe and more.
- SPACEPerplexity's open-source sandbox platform, the one behind every task in Perplexity Computer. It runs agent and user code in isolated Firecracker microVMs behind an HTTP API.
- durable-harnessVercel's adapters that run existing coding-agent harnesses (Pi, OpenCode, fx, Claude Code, Codex) as durable agents on a Workflow SDK World, so a crash or function timeout resumes the turn instead of losing it.
- MCP Events (SEP-3415)Draft SEP that adds an Events extension to the Model Context Protocol. A client subscribes to upstream events like a Slack message, a repo push or a PagerDuty incident, and the agent reacts when one arrives instead of waiting for a cron job or a user message.