Build durable agents with @eve.

Was super cool to see Agent Runs expand to cover use cases outside of @eve. Plus I implemented instrumentation hooks in fx like any other harness has so it could be instrumented.

Much like we did with @aisdk, we're bringing a truly open-source, runtime-agnostic solution to harness durability. We're extending the durability infra that powers @eve and Workflows to all harnesses, like Pi and OpenCode. Local, Vercel, or DIY. Fun fact: even Claude Code and Codex can be made durable (and observable!) this way. The catch: they're not (currently) designed for embedding, which makes them less efficient, less portable, and brings an extra sandbox requirement compared to Pi or Fx.

with @eve’s native Slack channel, scheduled runs can fan out into existing threads example: every morning, revisit each open question thread and post the investigation inside it just pass the optional threadTs to your Slack target. leave it out and eve starts a new thread

We're excited to have Amy Egan (@amyegan), Staff Community Engineer for @vercel, presenting "An Agent Is Just a Directory" at #AllThingsOpen! 2026.allthingsopen.org/sessi…

I've been building ecommerce agents for a while and tried many AI frameworks along the way. I must say: @eve is the first one that really clicked. I told @shardara this recently and he asked me why, so I thought it was worth sharing publicly. In my first AI consulting gigs (mostly custom shopping assistants) I was stunned by how much infra work it takes to ship an agent. I'd say 60–70% of my time went into infra, and only the rest into the actual AI work: context engineering, data, evals. That was insane tbh, because none of that infra felt custom to me. Most frameworks either didn’t help much with infra, or if they did, they forced clunky abstractions on the AI side, and I kept fighting the framework instead of doing my work. That's probably why so many folks say "don't use a framework, just build from scratch." I felt that too (we all have our Claudes and Codexes, right?), but going framework-less never felt right either. There’s so much repeatable stuff, and way too many footguns, to rebuild it every time. So for a long time I was looking for something very simple: 1. Pls pls handle infra for me. Durable execution, sandboxes, streaming, reconnects, subagents, file uploads that land in the sandbox, auth, web search, easy deployment. 2. LEAVE ME FREEDOM on the AI part. I want to own the harness, not have the framework own it for me. @eve is just the first one that ticks all these boxes. Bonus: every production agent quickly needs a UI and often a custom API. A playground, a context view, a domain-specific data viewer (inspired by @HamelHusain, highly recommend). With Eve + Next.js it’s all in a single repo (not even a monorepo!), deployed with one click. Framework-defined Infrastructure at its finest, it really feels good. btw, I come from front-end world and I remember exactly how the world looked before and after nextjs. Now it feels like this again, just with AI. Everything we do at the eCommerce AI Lab at @commerce_ui now runs on Eve: shopping assistants and analytics agents for our clients, plus our own company agent that lives in Slack. It all just works, and a huge amount of custom code just evaporated. Highly recommend

If you missed @andrew_barba's @eve presentation yesterday at Ship, then be sure to catch up in this 🧵!

It’s time to 🇺🇸-max. Beam is an American-made open-weight model by Reflection. And it’s now free on @vercel AI Gateway. Plug it into deployable @eve agents, start coding with @fx, or build your own harness. Freedom. Never bet against America.

Vercel drives in eve: eve.dev/docs/sandbox/vercel#…

Attending Vercel Ship? Join @andrew_barba today at 11:15 PDT to learn how to build agents and what's new in the @eve framework. vercel.com/ship/sf/session/e…

Built a code review agent for myself: - @mattpocockuk’s code review skill as the basis for the system prompt - @eve + Vercel Connect to access GitHub and Linear - GPT 6.1 Sol to power the agent Was honestly so easy and costs are very reasonable. I’m pumped!

We took @eve and gave it everything an employee has. An identity. Its own computer. A company credit card. A vault for logins. SOTA memory. Even a phone number. We put an enterprise control plane around it so your whole company can use one agent. kybernesis.ai/agent

build a multiplayer coding agent on Slack in 4 steps with @eve: 1️⃣ npx eve@latest init my-coding-agent 2️⃣ add the eve-code extension 3️⃣ /add channel/github 4️⃣ /add channel/slack deploy it, and you’ve got a cloud coding agent you can @ mention in any thread