v0 by Vercel vs Dust
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.
Dust is widening the agent-platform surface: multimodal tools, enterprise audit, model breadth.
Dust is shipping at a fast clip on three fronts that together define a serious agent platform: model breadth (Gemini 3.5 Flash, Grok 4.3, refreshed Anthropic lineup), agent capability (MCP tools can now return images the agent can actually see, plus context compaction for long runs), and enterprise readiness (workspace audit logs streamable to Datadog, Splunk, or any HTTPS sink). Integrations are getting versioned upgrades on the side (Asana MCP v2, Gmail labels and archive). The product is moving from 'chat with an agent' toward 'run agents in production with observability and multimodal I/O.'
Two clear directions: deeper enterprise GTM via SIEM-grade audit, and a more capable agent runtime that can see, remember, and act inside third-party SaaS. The MCP-image release in particular treats Model Context Protocol as a real I/O surface rather than a text-only RPC, which is where the broader MCP ecosystem is heading. Frequent model rotations suggest Dust is positioning as model-agnostic infrastructure rather than locking into one provider.
Next moves likely lean into the same arc: more MCP integrations with action verbs (write/delete/transition states), expanded multimodal returns (audio, structured documents), and finer-grained admin controls layered on top of the audit foundation - tool-usage policies, per-agent egress rules, or approval workflows.
See more alternatives to v0 by Vercel →
See more alternatives to Dust →