Vercel has released eve, an open-source framework for building, running, and scaling agents. The project is published as the npm package eve, licensed under Apache-2.0.
Building an agent should mean defining what it does. It should not mean assembling all the plumbing that an agent needs to run in production.
eve is the framework Vercel builds and runs its own agents on. According to Vercel post, it runs more than a hundred agents in production today.
eve is a filesystem-first framework for durable backend agents. You create an agent as a directory on disk. The directory is the contract.
Each file describes one component of the agent. At a glance, the tree shows what an agent is and does. It also shows where it lives and when it acts on its own.
The smallest agent that runs is two files. One sets the model. The other sets the instructions.
// agent/agent.ts
import { defineAgent } from "eve";
export default defineAgent({
model: "anthropic/claude-opus-4.8",
});The model is one line, and provider fallbacks are supported through AI Gateway. The instructions.md file becomes the system prompt that eve puts in front of every model call.
Vercel’s core idea is that agents have a shape. Every team kept rebuilding the same structure to meet the same needs. eve makes that shape into a framework.
The directory layout maps each capability to a folder. Here is the contract:
| Path | Role | Format |
|---|---|---|
agent.ts | The model it runs on, plus runtime config | TypeScript |
instructions.md | Who it is, prepended to every model call | Markdown |
tools/ | What it can do; filename becomes the tool name | TypeScript |
skills/ | What it knows; loaded only when the topic comes up | Markdown |
connections/ | Secure links to MCP servers and OpenAPI APIs | TypeScript |
sandbox/ | Optional override of the agent’s sandbox; seeds workspace files | Directory |
subagents/ | Specialist child agents it delegates to | Directory |
channels/ | Where it lives, like Slack or HTTP | TypeScript |
schedules/ | When it acts on its own, on a cron | TypeScript |
lib/ | Shared authored code used across the agent | TypeScript |
You add a tool, skill, channel, or schedule by adding a file. eve picks them up at build time and wires them in. There is no boilerplate to register them.
A tool is one TypeScript file with a Zod input schema. Its filename and place in the tree become its definition.
// agent/tools/run_sql.ts
import { defineTool } from "eve/tools";
import { z } from "zod";
export default defineTool({
description: "Run a read-only SQL query.",
inputSchema: z.object({ sql: z.string() }),
needsApproval: ({ toolInput }) => estimateScanGb(toolInput.sql) > 50,
async execute({ sql }) { /* ... */ },
});Vercel describes eve as ‘batteries included.’ Six production capabilities come with the framework:
Vercel published six agents it runs internally on eve:
Most teams assemble these pieces themselves for each new agent. The table below maps that work against what eve provides.
| Capability | Typical DIY stack | eve |
|---|---|---|
| Authoring | Custom loop, manual tool registration | Files in a directory, discovered at build |
| Durability | Bespoke state and retry handling | Checkpointed durable workflow per session |
| Code execution | Self-managed container or VM | Per-agent sandbox via swappable adapter |
| Approvals | Custom pause-and-resume logic | needsApproval field on any action |
| Surfaces | One integration per channel | One adapter file per channel |
| Observability | Stitched together from logs | OpenTelemetry traces and evals built in |
| Deploy | Provision infrastructure | vercel deploy, runs unchanged from local |
The comparison reflects eve’s documented capabilities. Specifics of other frameworks vary by version and setup.
You can scaffold and start a new agent with one command. It installs dependencies, scaffolds the project, and starts a dev server.
npx eve@latest init my-agenteve dev runs the agent locally with an interactive terminal UI. eve eval runs your test suites. eve build compiles inspectable artifacts under .eve/.
Because an eve agent is an ordinary Vercel project, vercel deploy ships it to production unchanged. The sandbox swaps to Vercel Sandbox without a code change.
npx eve@latest init, then deploy unchanged via vercel deploy.Check out the Repo, Product page, Docs and Technical details. Also, feel free to follow us on Twitter and don’t forget to join our 150k+ML SubReddit and Subscribe to our Newsletter. Wait! are you on telegram? now you can join us on telegram as well.
Need to partner with us for promoting your GitHub Repo OR Hugging Face Page OR Product Release OR Webinar etc.? Connect with us
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。