"could it run on cloudflare?" people kept asking that about Vercel's @eve . so I built Eden. one command, and then your Eve agent is live on your own @Cloudflare . same project, no rewrite. npx @moinulmoin/eden deploy fully open source 🧵

filed a bug on vercel's eve harness. they picked it up and shipped the fix in 3 days filed one on langchain. they assigned the fix to me, i wrote it, and the pr's been waiting on review for 6 weeks so i think we know which agent harness is gonna win

you can get a durable @eve agent session id from your web app before the user sends their first message by passing prewarm it unlocks use cases like: 1. setting the chat url (e.g. /s/) from the start, so a refresh mid-reply reopens the same chat 2. files can upload under that session before the message that uses them goes out 3. a support widget can put the session id on the ticket the moment it opens

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

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

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.

eve agents now have memory. Use built-in file memory, a memory service, or your own provider to retain context across sessions. 𝚎𝚟𝚎 𝚊𝚍𝚍 𝚖𝚎𝚖𝚘𝚛𝚢/𝚏𝚒𝚕𝚎

Create @SlackHQ shortcuts directly in eve. The eve Slack experience continues to improve with: ▪︎ Native command and shortcut support ▪︎ Understanding of previews and forwarded messages ▪︎ Definable thread reply policies