VercelEngineering PostOfficial Source

Sub-second artifact deployments are now supported in Vercel CLI

Vercel CLI can return a live URL in under a second for small static artifacts, making agent-generated reports and prototypes easier to share without a build step.

Vercel · Sep 17, 2026

Open Source Open Markdown Open JSON

Source Summary

With **Vercel CLI 59.16.0 or later**, eligible static artifacts can deploy in **under one second**. Vercel detects them, skips the build, and returns a live URL.

Practical Implication

Use `vercel deploy` as a lightweight publishing step for agent-generated prototypes, HTML reports, and previews when a full application build would add needless delay.

Agent-Ready Context

With **Vercel CLI 59.16.0 or later**, eligible static artifacts can deploy in **under one second**. Vercel detects them, skips the build, and returns a live URL.

Use `vercel deploy` as a lightweight publishing step for agent-generated prototypes, HTML reports, and previews when a full application build would add needless delay.

Instant deployment is limited to **10 HTML or Markdown files**, **5 MB total**, and `.html`, `.htm`, or `.md` files. Anything outside those bounds follows a different path.

Connected Context · Feed7 Judgment

This creates a very small delivery loop for agent-produced reports and prototypes: qualifying files can become shareable URLs without a build. It complements broader cloud-agent deployment workflows but sharply narrows the fast path to ten HTML or Markdown files and 5 MB, so it is an artifact-publishing primitive rather than a replacement for application deployment.

Vercel MCP can now deploy codeThe MCP capability closes the agent-to-deployment gap broadly; sub-second artifact deployment identifies a constrained class of outputs that can skip the build, while larger code deployments retain their normal controls and failure modes.Deployments now show billable duration and CPU minutesPer-deployment duration and CPU reporting can distinguish these build-skipping artifact publishes from agent-triggered deployments that consume build resources.Realtime multiplayer, automation, and you! — Idan Gazit, GitHubGitHub Next treats Markdown as a reviewable workflow boundary; this fast path additionally lets small Markdown outputs become immediately shareable deployment artifacts.How Sandstone grew 40x in 147 days on VercelSandstone shows preview deployments inside a production agent system, while the new CLI path narrows one lightweight option for previews that consist only of small static artifacts.

Context Map

infracoding#dev-ux#cloud-agents

Uncertainty

Instant deployment is limited to **10 HTML or Markdown files**, **5 MB total**, and `.html`, `.htm`, or `.md` files. Anything outside those bounds follows a different path.