这是一个开源的参考应用,用于在Vercel上构建和运行后台编码代理。它包含Web界面、代理运行时、沙箱编排和GitHub集成,让你不用一直开着笔记本就能从提示词生成代码改动。整个系统分三层:Web应用处理认证和聊天界面,代理作为持久工作流运行在Vercel上,沙箱提供文件系统、shell和预览端口等执行环境。核心设计是代理不跑在虚拟机里,而是通过工具与沙箱交互,这种分离是项目的关键。适合想fork后自行定制、构建自动化编码工作流的开发者。
查看英文原文
Open Agents Open Agents is an open source reference app for building and running background coding agents on Vercel. It includes the web UI, the agent runtime, sandbox orchestration, and the GitHub integration needed to go from prompt to code changes without keeping your laptop involved. The repo is meant to be forked and adapted, not treated as a black box. What it is Open Agents is a three layer system: [安装/使用命令见下方] The web app handles auth, sessions, chat, and streaming UI. The agent runs as a durable workflow on Vercel. The sandbox is the execution environment: filesystem, shell, git, dev servers, and preview ports. The key architectural decision: the agent is not the sandbox The agent does not run inside the VM. It runs outside the sandbox and interacts with it through tools like file reads, edits, search, and shell commands. That separation is the main point of the project: agent execution is not tied to a single request lifecycle sandbox lifecycle can hibernate and resume independently model/provider choices and sandbox implementation can evolve separately the VM stays a plain execution environment instead of becoming the control plane Current capabilities chat driven coding agent with file, search, shell, task, skill, and web tools durable multi step execution with Workflow SDK backed runs, streaming, and cancellation isolated Vercel sandboxes with snapshot based resume repo cloning and branch work inside the sandbox optional auto commit, push, and PR creation after a successful run session sharing via read only links optional voice input via ElevenLabs transcription Runtime notes A few details that matter for understanding the current implementation: Chat requests start a workflow run instead of executing the agent inline. Each agent turn can continue across many persisted workflow steps. Active runs can be resumed by reconnecting to the stream for the existing workflow. Sandboxes expose ports 3000 , 5173 , 4321 , and 8000 , can optionally use a configured