Vercel just shipped eve. Your agent is now a directory of files.

Vercel open-sourced eve on June 17.

It is a filesystem-first agent framework where your agent IS a folder structure — not a config file, not a pipeline, not a graph.

agent/
agent.ts
instructions.md
tools/
skills/
subagents/
channels/
schedules/

Every file maps to one capability. The tree IS the agent.

This is the Next.js playbook applied to agents. Convention over configuration. One file = one ability. No boilerplate, no wiring, no registration.

The technical depth is real:

Durable sessions — every conversation checkpoints. Agents can pause, crash, deploy, and resume exactly where they stopped. Built on the open-source Workflow SDK.

Sandboxed compute — agent-generated code runs in isolated containers. Docker locally, Vercel Sandbox in production. The model never touches your application runtime.

Human-in-the-loop — one field on any tool. The agent pauses, waits indefinitely, resumes on approval. Zero compute cost while waiting.

Subagents — same directory structure, nested. Parent calls child like a tool. Clean context, scoped tools, result handback.

Channels — Slack, Discord, Teams, Telegram, Twilio, GitHub, Linear. One command to add each. Same agent, every surface. Sessions move between them.

Evals built in — test suites in TypeScript, wired into CI. Every commit gets a preview deployment. Every model call and tool call produces an OpenTelemetry trace.

The numbers from Vercel's production use:

100+ agents running internally.
29% of all Vercel deployments now triggered by agents.
One data analyst agent handles 30,000 questions per month.
Their autonomous SDR costs $5,000/year to run, returns 32x that.
Support agent solves 92% of tickets without humans.

npm install eve. One command to scaffold. One command to deploy. The same directory runs on your laptop and in production.

Audit your agent architecture now.

If you are hand-rolling session persistence, sandbox isolation, or channel integrations, you are rebuilding what eve already ships. The convention-over-configuration pattern worked for web routes. It will work for agent capabilities.

Source: https://vercel.com/blog/introducing-eve
Verified: Vercel blog (June 17, 2026), GitHub repo (vercel/eve, 1.4k stars, Apache-2.0), npm package eve v0.11.6
Signal: Vercel is applying the Next.js playbook to agents — filesystem conventions replacing infrastructure code. When a platform company open-sources the framework they run internally, it resets the baseline for everyone else.