Vercel is introducing Eve, a file-based framework for AI agents that mirrors the project structure developers already know from Next.js. Agents begin as simple directories with Markdown files handling instructions and skills while TypeScript defines tools, then scale through folders for subagents, schedules, channels, and connections without requiring separate infrastructure glue.
Every agent needs streaming, models, durability, isolation, channels, and integrations.
The Agent Stack has them all: ▪︎ AI SDK ▪︎ AI Gateway ▪︎ Workflow SDK ▪︎ Sandbox ▪︎ Chat SDK ▪︎ Vercel Connect
𝚎𝚟𝚎 implements them with one command ↓https://vercel.com/blog/agent-stack
Start with an instructions.md file plus an optional agent.ts config, then drop typed functions into a tools folder or reusable procedures into skills. The layout auto-discovers components so the same codebase can expose Slack bots, web chats, or scheduled runs.
Workflows provide checkpointed execution that survives crashes and supports human approvals, while built-in evaluation suites can run on deploy or schedule. Sandboxed compute and model access through the existing AI SDK keep everything within one Vercel deployment flow.
Many users are excited about Vercel's Eve framework for building AI agents because of its simple one-command setup and clean developer experience that avoids complex configs.
No Digg Deeper questions have been answered for this story yet.
http://Eve.dev is Next.js for agents.
I built Next with a simple premise: 𝚙𝚊𝚐𝚎𝚜/𝚒𝚗𝚍𝚎𝚡.𝚓𝚜 is all you need. Put some React in there and you’re good to go.
Eve asks for even less. 𝚊𝚐𝚎𝚗𝚝/𝚒𝚗𝚜𝚝𝚛𝚞𝚌𝚝𝚒𝚘𝚗𝚜.𝚖𝚍. Put some English in there and you’re good to go.
Like Next, it embraces the filesystem. You can guess what 𝚝𝚘𝚘𝚕𝚜/𝚚𝚞𝚎𝚛𝚢-𝚍𝚋.𝚝𝚜 does. An agent is just a directory, whose entire spec fits in the tweet below.
And like Next on Vercel, it’s seamless to deploy. The infra, like Sandbox, Gateway, Workflow… is the output of your creation.
Introducing eve, an agent framework.
𝚊𝚐𝚎𝚗𝚝/ 𝚊𝚐𝚎𝚗𝚝.𝚝𝚜 𝚒𝚗𝚜𝚝𝚛𝚞𝚌𝚝𝚒𝚘𝚗𝚜.𝚖𝚍 𝚝𝚘𝚘𝚕𝚜/ 𝚜𝚔𝚒𝚕𝚕𝚜/ 𝚜𝚊𝚗𝚍𝚋𝚘𝚡/ 𝚜𝚌𝚑𝚎𝚍𝚞𝚕𝚎𝚜/
Like Next.js, for agents. https://vercel.com/blog/introducing-eve
React → http://ai-sdk.dev Next.js → http://eve.dev
@aisdk is more relevant than ever, given the intense model competition landscape. Just today, GLM 5.2, an open model, surpassed Opus 4.8 in our Next.js Evals (http://nextjs.org/evals) 🤯
But the world needs a practical solution for how to build and deploy agents. Just like React needed Next.js to solve the task of building an actual web application. And that's eve.
eve looks like a very promising agent framework.
Built-in: - Durable execution - Sandboxed compute - Human-in-the-loop approvals - Subagents - Evals - and more
I like the emphasis on evals right away.
Should I do a tutorial on it?
Introducing eve, an agent framework.
𝚊𝚐𝚎𝚗𝚝/ 𝚊𝚐𝚎𝚗𝚝.𝚝𝚜 𝚒𝚗𝚜𝚝𝚛𝚞𝚌𝚝𝚒𝚘𝚗𝚜.𝚖𝚍 𝚝𝚘𝚘𝚕𝚜/ 𝚜𝚔𝚒𝚕𝚕𝚜/ 𝚜𝚊𝚗𝚍𝚋𝚘𝚡/ 𝚜𝚌𝚑𝚎𝚍𝚞𝚕𝚎𝚜/
Like Next.js, for agents. https://vercel.com/blog/introducing-eve
@kumard_3 Yes. In a very tangible way I can describe in this tweet.
Deploying eve basically gives you an API backend.
And then you can query it with a 𝚞𝚜𝚎𝙴𝚟𝚎𝙰𝚐𝚎𝚗𝚝() hook we produce, for Next, Vite, TanStack to consume.
https://eve.dev/docs/guides/frontend/overview
@rauchg @lgrammel @aisdk when ai dot dev?
@rauchg stop shipping guillermo
i dont have time to experiment with all of this
@rauchg cool and this will pair easily with next ?
@rauchg @eve_bouff what do we think
@shadcn @rauchg @lgrammel @aisdk What about http://web-ai-sdk.dev ? Anyway, in total love Eve 👀 hahaha
@rauchg React made HTML programmable.
AI is making English programmable.
@rauchg Very intrigued. So it goes even more abstract, just need to know logic and English?
@rauchg what a great fucking name through and through
@tamas__szuromi @rauchg sure does. any company serious about building agents must iterate with evals. I could not imagine launching eve without it. in fact the entire eve e2e test suite is built on the evals and you can look at the runs directly on GitHub
@rauchg Does (or will) the sandbox also support MCX? https://github.com/microsoft/mxc
@rauchg In the demo on stage, the skill.md file didn’t have YAML front matter. Will eve need a new skill spec? Or is instruction.md the new standard
@rauchg @cramforce Does eve handle context management?
@rauchg @evilrabbit_ banger drop! will try tomorrow
@elie2222 @rauchg @evilrabbit_ It already does support any oauth API or MCP
@rauchg Can I use it without using it with next? Maybe nodejs ?
@rauchg @evilrabbit_ Looks cool. When do you think Vercel Connect expands to support any api? Or that’s not planned?
