v0 by Vercel vs Ably
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.
Ably pivots its developer surface toward AI agents as first-class consumers
Ably's developer surface has been visibly pivoting toward AI agents over the last six weeks. The CLI hit v1.0 with structured JSON output envelopes, hint fields for self-healing agents, and unified --force semantics. Two weeks later v1.1 added `ably init`, which installs the CLI plus Agent Skills bundles directly into Claude, Cursor, Windsurf, and VS Code in one step. A new AI Transport SDK lands separately, with end-to-end tool-calling and React providers for the Vercel AI SDK.
Ably is building two integration stories in parallel — agents as CLI users (via Agent Skills) and agents as transport consumers (via the AI Transport SDK). Together they bracket the workflow: agents read live data through the SDK and operate Ably itself through the CLI. The traditional client-library stream (JS, Python, Laravel) continues at steady pace in the background, with LiveObjects formally graduating to GA on the protocol-6 update.
Expect the AI Transport SDK to add tool-call adapters for at least one more AI runtime beyond Vercel — most likely the OpenAI Agents SDK or Anthropic's Claude Agent SDK — and Agent Skills coverage to expand to additional AI clients (Cline, Aider, Continue). Watch for the LiveObjects API to surface inside the chat/AI surfaces.
See more alternatives to v0 by Vercel →
See more alternatives to Ably →