Vercel Releases Eve: An Open-Source AI Agent Framework Where Each Agent is a Directory of Files Mapped to Capabilities
Vercel has launched eve, an open-source framework for constructing, working, and scaling brokers. The challenge is printed because the npm bundle eve, licensed underneath Apache-2.0.
Building an agent ought to imply defining what it does. It shouldn’t imply assembling all of the plumbing that an agent wants to run in manufacturing.
eve is the framework Vercel builds and runs its personal brokers on. According to Vercel put up, it runs greater than a hundred brokers in manufacturing at this time.
What is eve?
eve is a filesystem-first framework for sturdy backend brokers. You create an agent as a listing on disk. The listing is the contract.
Each file describes one element of the agent. At a look, the tree exhibits what an agent is and does. It additionally exhibits the place it lives and when it acts by itself.
The smallest agent that runs is two information. One units the mannequin. The different units the directions.
// agent/agent.ts
import { outlineAgent } from "eve";
export default outlineAgent({
mannequin: "anthropic/claude-opus-4.8",
});The mannequin is one line, and supplier fallbacks are supported by means of AI Gateway. The directions.md file turns into the system immediate that eve places in entrance of each mannequin name.
An agent is a listing
Vercel’s core concept is that brokers have a form. Every group saved rebuilding the identical construction to meet the identical wants. eve makes that form into a framework.
The listing structure maps every functionality to a folder. Here is the contract:
| Path | Role | Format |
|---|---|---|
agent.ts |
The mannequin it runs on, plus runtime config | TypeScript |
directions.md |
Who it is, prepended to each mannequin name | Markdown |
instruments/ |
What it could actually do; filename turns into the software identify | TypeScript |
abilities/ |
What it is aware of; loaded solely when the subject comes up | Markdown |
connections/ |
Secure hyperlinks to MCP servers and OpenAPI APIs | TypeScript |
sandbox/ |
Optional override of the agent’s sandbox; seeds workspace information | Directory |
subagents/ |
Specialist youngster brokers it delegates to | Directory |
channels/ |
Where it lives, like Slack or HTTP | TypeScript |
schedules/ |
When it acts by itself, on a cron | TypeScript |
lib/ |
Shared authored code used throughout the agent | TypeScript |
You add a software, talent, channel, or schedule by including a file. eve picks them up at construct time and wires them in. There is no boilerplate to register them.
A software is one TypeScript file with a Zod enter schema. Its filename and place within the tree turn into its definition.
// agent/instruments/run_sql.ts
import { defineTool } from "eve/instruments";
import { z } from "zod";
export default defineTool({
description: "Run a read-only SQL question.",
inputSchema: z.object({ sql: z.string() }),
needsApproval: ({ toolInput }) => estimateScanGb(toolInput.sql) > 50,
async execute({ sql }) { /* ... */ },
});What ships within the field
Vercel describes eve as ‘batteries included.’ Six manufacturing capabilities include the framework:
- Durable execution: Every dialog is a sturdy workflow, with every step checkpointed. A session can pause, survive a crash or a deploy, and resume the place it stopped. This is constructed on the open-source Workflow SDK.
- Sandboxed compute: Agent-generated code is handled as untrusted. Every agent will get its personal sandbox for shell instructions, scripts, and file reads and writes. The backend is an adapter, working on Vercel Sandbox when deployed and on Docker, microsandbox, or just-bash domestically.
- Human-in-the-loop approvals: Any motion could be set to require approval. The agent pauses there and waits, indefinitely if wanted, with out consuming compute. Once permitted, eve continues from the place it left off.
- Secure connections: A connection is a file pointing at an MCP server or an OpenAPI-compatible API. eve brokers the auth, and the mannequin by no means sees the URL or credentials. At launch, brokers can join to Slack, GitHub, Snowflake, Salesforce, Notion, and Linear.
- Channels: The identical agent serves each floor. The HTTP API is on by default, with Slack, Discord, Teams, Telegram, Twilio, GitHub, and Linear included. One channel can hand off to one other.
- Tracing and evals: Every run produces a hint utilizing normal OpenTelemetry spans. They export to Braintrust, Honeycomb, Datadog, or Jaeger. Evals are scored check suites you run domestically or wire into CI.
Use circumstances, with actual examples
Vercel printed six brokers it runs internally on eve:
- d0, the info analyst: Its most-used inner software, dealing with greater than 30,000 questions a month. Every question is scoped to the asker’s personal permissions.
- Lead Agent, the autonomous SDR: It works each new lead and follows up by itself. Vercel says it prices about $5,000 a yr and returns 32 occasions that, maintained part-time by one engineer.
- Athena, the gross sales cockpit: RevOps constructed it in six weeks with out engineers. It solutions pipeline questions from Snowflake and Salesforce in plain language.
- Vertex, the help engineer: It handles tickets throughout the assistance middle, docs, and Slack. Vercel studies it solves 92% of tickets by itself and escalates the remainder.
- draft0, the content material agent: It runs a assessment pipeline that catches evident points earlier than a human editor sees the piece.
- V, the routing agent: Tasks go to V in Slack first. V routes each to the agent that may reply it.