Twitter/X

Eve.dev, presented by @rauchg, positions itself as "Next.js for agents" using a…

Brief

Eve.dev, presented by @rauchg, positions itself as "Next.js for agents" using a filesystem-first model: an agent is just a directory (agent/agent.ts, agent/instructions.md, tools/, skills/, sandbox/, schedules/) where instructions.md can be plain English. Vercel introduced the 'eve' framework and says deployment and infra (Sandbox, Gateway, Workflow) are generated automatically.

Source evidence

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.

Vercel (@vercel)

Introducing eve, an agent framework.

𝚊𝚐𝚎𝚗𝚝/
𝚊𝚐𝚎𝚗𝚝.𝚝𝚜
𝚒𝚗𝚜𝚝𝚛𝚞𝚌𝚝𝚒𝚘𝚗𝚜.𝚖𝚍
𝚝𝚘𝚘𝚕𝚜/
𝚜𝚔𝚒𝚕𝚕𝚜/
𝚜𝚊𝚗𝚍𝚋𝚘𝚡/
𝚜𝚌𝚑𝚎𝚍𝚞𝚕𝚎𝚜/

Like Next.js, for agents.
vercel.com/blog/introducing-…

— https://nitter.net/vercel/status/2067180054979936413#m