2 min read
Add as a preferred source on Google

Vercel Adds Persistent Storage and Background Workers for AI Agents

Daemons and MCP Events entered public beta, while Drives became generally available for Vercel Sandbox on all plans.

A compact storage drive beside an open compute enclosure / TokenPost.ai
A compact storage drive beside an open compute enclosure / TokenPost.ai

Vercel is adding background workers and persistent file storage for AI agents, giving jobs a way to run beyond individual requests and workspaces a way to persist between sandbox sessions.

At its Ship 2026 event on Oct. 15, the company put Vercel Daemons into public beta, made Vercel Drives generally available for Vercel Sandbox and moved Vercel Connect’s MCP Events feature into public beta.

Daemons run as containers on Vercel’s Fluid compute. They can take work from queues, databases or third-party systems without requiring an HTTP server. Vercel maintains the configured number of instances and restarts them if they exit or crash.

Drives store files separately from a sandbox’s runtime. Developers can mount the same drive in a later sandbox session, keeping files available after the earlier sandbox ends. A drive can also be forked into separate writable copies, allowing multiple agents to start with the same workspace and make changes independently. Drives are generally available for Vercel Sandbox on all plans.

MCP Events lets apps and agents subscribe to webhook events from compatible MCP servers. Vercel Connect manages subscriptions and authenticated event delivery, so connected applications can receive notices when an event occurs.

The three features address separate parts of agent workflows: background processing, files that persist across sandbox runs and event delivery from compatible services. Drives are generally available, while Daemons and MCP Events remain in public beta.

Simon Yoon

Reporter

Simon Yoon reports on blockchain technology for TokenPost. Send corrections or tips to info@tokenpost.com.

Loading…