v0 by Vercel vs Buildkite
Side-by-side trajectory, velocity, and editorial themes.
v0 turns the agent into a real shell user — terminal commands, OAuth MCP, browser screenshots, all in two weeks.
v0 ships at very high cadence, mixing small daily fixes with substantive agent-capability work. The May releases gave the agent the ability to run terminal commands (with per-command permission prompts), cut sandbox startup time by 50%, added OAuth-authorized MCP server support in the platform API, and made Claude Opus 4.7 Fast a configurable model option. Surrounding work — Snowflake account picker, browser screenshots in previews, .riv file support, design-mode element screenshots — pushes v0 further into 'real builds, not just UI prototypes.'
v0 is moving from AI-assisted UI generation toward an AI coding agent that owns the full build-and-deploy loop. Terminal access, faster sandboxes, OAuth MCP, and tight Vercel/Snowflake integrations are platform plumbing for production work, not prototyping. Model coverage stays at the cutting edge — Opus 4.7 Fast landed as a selectable model the same week it was announced — and the bug-fix discipline shows a team treating v0 as a maintained engineering tool, not a demo surface.
Next likely move is longer-running or background agent work — scheduled runs, async tasks, or an agent that owns a Vercel project across days. The combination of terminal execution + sandbox speed + MCP is the foundation; what's missing is persistence.
AI-agent skills and OAuth Token Exchange land — Buildkite is courting both Claude/Cursor users and security teams.
Buildkite is shipping in two strong directions at once. On platform/security: OAuth 2.0 Token Exchange (RFC 8693) replaces long-lived API tokens with IdP-minted short-lived ones, and per-user API rate limits stop one runaway script from starving an org's quota. On surface area: official Buildkite skills for Claude Code, Cursor and similar AI coding agents teach agents how to use the platform, plus broader GitHub event triggers for incremental Actions migration. Smaller UX work (new build page list view, queue search, cluster sort) rounds out a heavy ship cadence.
Two arcs are converging: lowering the on-ramp for teams migrating off GitHub Actions (more triggers, agent-friendly skills, cleaner UI) and meeting the security posture larger customers ask for in procurement (short-lived tokens, scoped per-user limits). The agent-skills release in particular signals Buildkite expects pipeline configuration to increasingly be authored or modified by AI agents, and is moving to teach them in Buildkite's own voice.
Expect more skills coverage across specific Buildkite features (dynamic pipelines, OIDC federation patterns) and follow-on auth work — OIDC-based agent authentication, finer scopes on exchanged tokens. The GitHub Actions migration push will likely add equivalents for less common triggers (deployments, workflow_dispatch) to remove remaining excuses to stay.
See more alternatives to v0 by Vercel →
See more alternatives to Buildkite →