Drives for Vercel Sandbox: persist the workspace, not the run

UpdatedSeptember 23, 2026

Vercel Sandbox Drive persists workspace across runs

Vercel put Drives for Sandbox in public beta on 22 September 2026. The useful part is not a bigger temporary disk. It is a durable volume you create once, mount into a sandbox, and still have after that sandbox is gone.

That split matters if you are running coding agents. A sandbox is a good place to execute a task. It is a bad place to be the system of record for the checkout, the installed dependencies, and the files the agent just wrote. Kill the sandbox and that disk goes with it. The next run starts from an empty tree unless you rebuild it from git, a tarball, or some side store you operate yourself.

This is an excerpt. Read the full post at otf-kit.dev/blog/vercel-sandbox-drives-agent-workspace — full-stack kits your AI coding agent can actually ship to production. Browse the kits →

#ai-tools #agents #architecture

Comments

Join the discussion

No comments yet. Be the first to comment.

More from this blog

Queue backpressure on an owned backend: refuse the burst before the pool melts

Agent runs, vendor webhook fan-out, and retry storms arrive as a sudden pile of HTTP calls on an API you operate. The database pool and the worker processes behind that API are a fixed budget. Once ev

Sep 24, 20261 min read

Queue backpressure on an owned backend: refuse the burst before the pool melts

Circuit breakers on an owned backend: fail fast when the AI vendor fails

When a downstream AI or vendor HTTP dependency starts failing, the owned API should stop waiting on it. A circuit breaker opens after a measured run of failures and returns a cached, stale, or degrade

Sep 24, 20261 min read

Circuit breakers on an owned backend: fail fast when the AI vendor fails

Park failed jobs in a DLQ with reason, snapshot, and replay — not silent drop

On an owned backend, a failed background job belongs in a dead-letter queue with a failure reason, a payload snapshot, an attempt count, timestamps, the original queue identity, and a human or agent r

Sep 23, 20261 min read

Park failed jobs in a DLQ with reason, snapshot, and replay — not silent drop

Fail health, drain in-flight requests, then exit — not kill -9 mid-request

On an owned production API, SIGTERM is not an invitation to kill -9 the process while clients still have open requests. After you leave the sandbox and you own the Node process behind a load balancer

Sep 23, 20261 min read

Fail health, drain in-flight requests, then exit — not kill -9 mid-request

Rotate production secrets with dual-key overlap, not an edit to .env

Sandbox credentials are disposable. Production credentials on a backend you own are not. Once the process is serving real traffic, rotating a database password, a webhook signing secret, a provider AP

Sep 23, 20261 min read

Rotate production secrets with dual-key overlap, not an edit to .env

OTF — kits your AI coding agent can ship to production

640 posts

Engineering notes on shipping production apps with AI coding tools — Claude Code, Cursor, Codex, Lovable, Bolt — and the stack underneath: React Native, Expo, Next.js, Supabase. Honest takes on what works, what breaks, and the full-stack kits that get you to production faster. By OTF.

Command Palette

Comments

More from this blog