What shipped in Vercel
17 releases, newest first.
Data Cache moves to Runtime Cache
On October 30, 2026, Vercel Data Cache started moving to Runtime Cache. Next.js fetch caching and unstable_cache switch over on every version without code changes. On Pro, each project and environment gets its own Runtime Cache storage allocation, with 8x the space of Data Cache's previous team-wide pool. Enterprise projects get 10x their previous Data Cache storage. After a team migrates, Data Cache reads and writes that were previously unbilled are charged at Runtime Cache pricing. Rates start at $0.40 per million read units and $4.00 per million write units, and vary by region. Hobby teams get 1 million read units and 200,000 write units free each month across all projects. On Pro, usage draws from the $20 monthly infrastructure credit, and anything beyond it is billed at regional rates. Teams created on or after October 30, 2026 use Runtime Cache by default. Existing Hobby teams migrate on November 29, 2026. Vercel notifies Pro teams of their migration date. Enterprise account teams contact those customers with migration details. Existing Hobby and Pro teams can opt in early from the team's CDN settings, and Runtime Cache pricing applies as soon as they opt in.
Source for Data Cache moves to Runtime Cache (opens in a new tab)Daemon service bindings
On October 30, 2026, Vercel Daemons could call the services in their deployment through service bindings. A binding on the daemon names the target service and the environment variable that receives the service's URL. The daemon calls that URL like any other HTTP endpoint. Vercel handles the internal routing, authentication, and TLS, and the service stays private. Bindings point one way: services cannot bind to daemons. Each instance keeps calling the deployment that started it, even after a promotion or rollback.
Source for Daemon service bindings (opens in a new tab)Daemon liveness checks
On October 30, 2026, Vercel Daemons added HTTP liveness checks. A livenessProbe in the daemon configuration points at an HTTP endpoint that returns an error status when the daemon is no longer healthy. Vercel periodically requests the endpoint and restarts the daemon's container when the check fails.
Source for Daemon liveness checks (opens in a new tab)Vercel Plugin in Antigravity
On October 29, 2026, the Vercel Plugin became available in the Google Antigravity marketplace. It gives an Antigravity agent guidance on Vercel APIs and recommended patterns, with skills for products such as the AI SDK, Vercel Functions, and Workflow. Install it from Customizations, Marketplace in the Antigravity app.
Source for Vercel Plugin in Antigravity (opens in a new tab)Separate AI crawler and assistant firewall rules
On October 29, 2026, the AI Bots managed ruleset in Vercel Firewall could log or block AI crawlers and AI assistants separately. Vercel describes AI crawlers as bots that collect content for indexing and model training, and AI assistants as bots that fetch pages in response to user actions or search queries. Vercel updates the rules as new bots are added. Configure it under the project's Security, Firewall, Rules, then Bot Management. vercel firewall diff reviews the changes and vercel firewall publish applies them. The ruleset is available on all plans.
Source for Separate AI crawler and assistant firewall rules (opens in a new tab)Node.js 26 LTS on Vercel
On October 29, 2026, Node.js 26 LTS became generally available for builds and Vercel Functions, and it is the default for new projects. Built-in fetch uses HTTP/2 by default through Undici 8. The release includes the Temporal API and V8 14.6, which adds Map.prototype.getOrInsert(). If engines.node in an existing project's package.json allows 26, such as >=20, the next deployment uses Node.js 26. Set engines.node to 26.x to choose it directly. Prebuilt deployments need Vercel CLI 65.8.0 or later. Set VERCEL_FETCH_DISABLE_H2 to 1 and redeploy to keep HTTP/1.1 in Functions. Minor and patch updates to Node.js 26 roll out automatically.
Source for Node.js 26 LTS on Vercel (opens in a new tab)Vercel Connect webhook triggers
On October 29, 2026, Vercel Connect added webhook triggers for Resend, X, Twilio, Notion, and Telegram. Connect receives events, such as Telegram bot messages or emails received by a Resend domain, verifies the requests, handles provider heartbeats and verification challenges, and forwards them to an endpoint in a Vercel project. Connect registers webhooks automatically for Resend and Telegram. For Twilio, Notion, and X, copy the webhook URL from Connect and finish setup in the provider's settings. These connectors join existing trigger support for Slack, Discord, Microsoft Teams, GitHub, and Linear.
Source for Vercel Connect webhook triggers (opens in a new tab)Finer IP geolocation
On October 29, 2026, Vercel IP geolocation started resolving visitor locations with finer network granularity. Vercel says it delivers city-level data for nearly all requests and postal-code data for 90% of traffic, and that the data is refreshed more often. It is on for every project with no code or configuration change. Existing geolocation headers and the geolocation() helper in @vercel/functions return the same fields for Vercel Functions and Routing Middleware. Subnets announced from a hosting provider in a different country than their regional internet registry record now resolve to the data center where the traffic terminates. Some visitors can resolve to a different city or country, most often traffic from VPNs, hosting providers, and leased IP ranges.
Source for Finer IP geolocation (opens in a new tab)Box Mount in Vercel Sandbox
On October 28, 2026, Box Mount became available in private preview for Vercel Sandbox. It syncs a Box folder with a directory in the sandbox so an agent can read and write those files through the filesystem. Unmount before stopping the sandbox, and the agent's writes are in Box after the sandbox is deleted. The sync process and the agent run as separate sandbox users, so the Box credentials stay out of the agent's workspace. Request access from Box, then follow Vercel's Box Mount documentation.
Source for Box Mount in Vercel Sandbox (opens in a new tab)Paseo agents on Vercel Sandbox
On October 28, 2026, Paseo could run fx, Codex, Claude Code, OpenCode, and Pi in Vercel Sandbox through the Vercel Sandbox plugin. An agent started from Paseo on a laptop can be controlled from a phone after the laptop is closed. Stopping a sandbox saves files and conversation history. Active processes stop with the sandbox. The Vercel AI Gateway key is entered once during setup and reused for model requests, outside the sandbox. Enable plugins in Paseo under Settings, Plugins, then run paseo plugin add vercel-labs/paseo-vercel-sandbox.
Source for Paseo agents on Vercel Sandbox (opens in a new tab)Agents can enable Web Analytics from the CLI
On October 28, 2026, Vercel CLI stopped requiring an interactive terminal to enable Web Analytics or Observability Plus, so an agent can turn them on. From a linked project directory, run vercel project web-analytics enable or vercel project observability enable. Enabling Observability Plus requires the team to already be subscribed to it. This requires Vercel CLI 64.2.0 or later.
Source for Agents can enable Web Analytics from the CLI (opens in a new tab)Vercel Plugin in OpenCode
On October 27, 2026, the Vercel Plugin became available in OpenCode 2. It gives on-demand guidance on Vercel APIs and recommended patterns, with skills for the AI SDK, Vercel Functions, Workflow, and more, plus specialist agents for deployment, performance optimization, and AI application design. /vercel:deploy deploys a project and /vercel:env manages environment variables. Install it with opencode plugin add github:vercel/vercel-plugin, then run /mcps, select vercel, and sign in to connect the Vercel MCP server.
Source for Vercel Plugin in OpenCode (opens in a new tab)Vercel Agent sessions use fewer tokens
On October 27, 2026, Vercel said Agent sessions in the dashboard and Slack cost 67% less on average. Agent uses fewer tokens per session and reuses more of the prompt cache, including in long Slack threads. Updated Vercel CLI skills give agents clearer guidance for common workflows and error recovery, and other agents that use those skills get the same guidance. Billing rates are unchanged: paid sessions are billed at the model provider's inference rates plus a Vercel Agent fee of $0.25 per million tokens. The change is already live.
Source for Vercel Agent sessions use fewer tokens (opens in a new tab)Vercel Agent can validate alerts before paging
On October 26, 2026, Vercel Agent can investigate alerts from Vercel monitors before they reach a paging system. With validation enabled for a webhook destination, only alerts Agent classifies as Critical are sent to it. Turn it on from a monitor's notification settings by selecting Critical Only on that destination, or with the Vercel CLI command vercel monitors notifications and --critical-only. Agent checks logs and metrics, and a monitor can include context to guide that check. Alert validation is available on Pro and Enterprise plans with Observability Plus, which includes 10 Agent investigations per billing cycle. Additional investigations are billed separately.
Source for Vercel Agent can validate alerts before paging (opens in a new tab)AI Gateway logs show session affinity
On October 18, 2026, Vercel AI Gateway logs gained a Sessions view. It groups requests into sessions and shows how session affinity routed each one, including the coding agent or app, cost, models, providers, and how much of the input was cached. Session affinity runs by default on text and chat requests. To group requests yourself, send the same sessionId in providerOptions.gateway, or the same x-session-id header, on every request in a conversation.
Source for AI Gateway logs show session affinity (opens in a new tab)Vercel Daemons public beta
On October 15, 2026, Vercel Daemons entered public beta. Daemons run containers on Fluid compute, deployed with the app, that pull work from Vercel Queues, databases, or third-party systems without an HTTP server. That includes queue consumers (Vercel Queues poll mode, Celery, BullMQ, RabbitMQ, or Kafka), Temporal or Cadence workers, and self-hosted CI runners for GitHub Actions, GitLab, or CircleCI.
Source for Vercel Daemons public beta (opens in a new tab)Python runtime generally available
On October 15, 2026, Python became a generally available runtime on Vercel. FastAPI, Flask, and Django apps are recognized automatically, CPython runs on Linux with uv and pyproject.toml, and request-driven apps can use Fluid compute while long-running pull-based work can use Vercel Daemons. Python SDKs in the same release include Sandbox, an AI SDK beta, a Workflow SDK beta, Queues (beta), Connect, and Blob.
Source for Python runtime generally available (opens in a new tab)
Updated