Trending #8 on GitHub today, 4.9k stars, 406 stars per day. The numbers aren't explosive, but digging into the repo reveals something worth attention.
vercel-labs/open-agents is not another toy "AI writes code" project. It is a complete reference architecture for cloud-based coding agents—authentication, session management, sandbox isolation, Git integration, and automatic PR creation, all included.
Three-Layer Architecture
The project splits itself into three layers:
- Web layer: Auth, sessions, chat UI, streaming. Built on Next.js.
- Agent workflow: Runs as a durable workflow on Vercel, supporting streaming output and mid-execution cancellation.
- Sandbox VM: An isolated execution environment with filesystem, shell, git, dev servers, and preview ports.
The key insight is this line: "the agent is not the sandbox." The agent runs outside the sandbox and interacts with the VM through tool calls. This means the sandbox can hibernate, snapshot, and resume without affecting the agent's state.
This design is smarter than most approaches that bind the agent and sandbox together. You know those coding agents that lose everything when the connection drops halfway through? This is what they failed to isolate properly.
What It Can Do
Current capabilities:
- Chat-driven coding agent with file manipulation, search, shell commands, web access tools
- Git repository cloning and branch operations
- Automatic commit, push, and PR creation
- Session sharing via read-only links
- Voice input (ElevenLabs transcription)
One-click deploy to Vercel. Configure Postgres URL, Better Auth secret, GitHub App, and Vercel OAuth, and you are running.
Who Should Care
If you are—
- Looking to build your own coding agent service on Vercel infrastructure
- Evaluating Vercel sandboxes as an Agent execution environment
- Needing durable workflow patterns (multi-step, interruptible, resumable)
This repo is a solid starting point. 962 commits shows this is not a three-day hack—there is real maintenance behind it.
If the Vercel ecosystem is not your thing, the architectural patterns here still have reference value. Agent-sandbox separation, durable workflow for state management, snapshot recovery—these patterns translate to other cloud platforms too.
Caveats
The dependency on Vercel's ecosystem runs deep. Postgres, Better Auth, Vercel Sandboxes, Vercel OAuth, GitHub App—the whole stack is locked into Vercel. Migrating to AWS or self-hosting would take serious work.
Also, 263 branches, 28 open issues, 22 PRs—high activity for an open-source reference project, which means it is still in rapid iteration. Expect API changes.
Main sources: vercel-labs/open-agents GitHub, Vercel Labs