https://t.co/uNXS9jEgpg 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.
Today we're open sourcing https://t.co/p76KVdY7dG, a reference platform for cloud coding agents.
You've heard that companies like Stripe (Minions), Ramp (Inspect), Spotify (Honk), Block (Goose), and others are building their own "AI software factories". Why?
1οΈβ£ On a technical level, off-the-shelf coding agents don't perform well with huge monorepos, don't have your institutional knowledge, integrations, and custom workflows.
2οΈβ£ On a business level, the moat of software companies will shift from 'the code they wrote', to the 'means of production' of that code. The alpha is in your factory.
Open Agents deploys to our agentic infrastructure: Fluid for running the agent's brain, Workflow for its long-running durability, Sandbox for secure code execution, AI Gateway for multi-model tokens.
(Because of our focus on Open SDKs and runtimes, this codebase is a gem even if you're not hosting on Vercel.)
TL;DR: if you're building an internal or user-facing agentic coding platform, deploy this:
https://t.co/xdsc42nbDN
3 months ago I started building a coding agent that runs in the cloud.
It's since written every line of code I've shipped, including itself.
Today, I'm open sourcing it. Introducing Open Agents.
Also major shout out to @willsather who has:
1) overtaken me in the internal leaderboard (I was at AIE last week π)
2) shipped some of the best recent updates (git panel, ci auto fix, file viewer, redesigned sidebar)
and @nishimiya who shipped the awesome landing page!