eve-software-factory-template README

The project's README from github.com/vercel-labs/eve-software-factory-template. As one markdown file: README.md.

eve Software Factory Banner

eve Software Factory Template

Docs Agent Stack MIT License

Meet Foreman, an eve software factory that puts AI agents on every stage of the development loop and keeps people on the judgment calls.

Foreman takes tasks from GitHub and Linear, moves each one through four stations, and delivers a reviewed draft pull request on your repository. You review, mark ready, and merge.

Deploy with Vercel

How it works

Each station is its own agent with its own instructions, sandbox, and tools. The Reviewer sees only the pushed branch, never the Implementer's reasoning. Between runs, Foreman keeps a factory brain: notes about your repository that every run starts from. See the pipeline and factory memory for the full picture.

How work arrives

Deploy

Deploy with Vercel

The Vercel deploy flow sets up everything: the GitHub connector, Linear connector, Vercel Blob store, and a prompt for the FACTORY_REPO and FACTORY_LABEL environment variables.

Two things must line up before the first deployment can finish. FACTORY_REPO must name a real repository in owner/repo format, and the GitHub App behind the connector you select must be installed with access to that repository. The deployment clones FACTORY_REPO up front to prewarm the station sandboxes, so a repository the app cannot reach fails the deploy with a Cannot access <owner/repo> error; install the app on the repository (or fix the value), then redeploy.

Configuration (see .env.example):

Variable Required Default What it does
FACTORY_REPO Yes — An existing GitHub repository in owner/repo format; the selected GitHub App must have access to it (the deploy fails otherwise)
FACTORY_SETUP_COMMAND No — Runs once inside the sandbox checkout at build time (e.g. pnpm install), so every run starts with dependencies already installed
FACTORY_LABEL No factory The issue label that hands an issue to the factory
FACTORY_BRANCH_PREFIX No factory/ Branch prefix marking the factory's own PRs, which are the only branches automated CI fixes touch
FACTORY_BOT_NAME No the GitHub App's slug The @mention name, resolved from the connector automatically when unset
GITHUB_CONNECTOR / LINEAR_CONNECTOR Yes — Set automatically from Vercel Connect connector UIDs

Local development

Link the project you deployed (or a fresh one), pull its environment, and start the TUI:

vercel link
vercel env pull
pnpm dev

Hand the agent a task ("users report the password reset email arrives twice, fix it") and watch the four stations fire in order, ending in a draft PR on FACTORY_REPO. Local runs are treated as untrusted, so changes to GitHub wait for your approval in the TUI.

Resources

Explore more templates

eve-software-factory-template (vercel-labs/eve-software-factory-template)

Searching Database…

这是什么?Foreman 是一个 “eve Software Factory”,让 AI 智能体参与开发循环的每个环节,同时把判断决策权留给人类。它从 GitHub 和 Linear 拉取任务,经过四个智能体工位处理,最后交付一个经审查的草稿 pull request 供你合并。
这是聊天机器人,还是自动化的智能体流水线?它是自动化多智能体流水线,不是聊天助手:分类器(Classifier)、分析师(Analyst)、实现者(Implementer)和审查者(Reviewer)各自作为独立智能体运行,拥有自己的沙箱和工具,不过你也可以通过 @提及或本地 TUI 与它交互。
Foreman 怎么部署?使用 Vercel 部署流程,它会设置 GitHub 连接器、Linear 连接器和 Vercel Blob 存储,并提示你填写 FACTORYREPO 和 FACTORYLABEL 环境变量。
部署之前需要什么?你需要一个现有的 GitHub 仓库(owner/repo 格式),并且所选的 GitHub App 已实际安装并被授予对该仓库的访问权限;Linear 集成是可选的,用于从 Linear 委派任务。
部署时最主要的坑是什么?如果 FACTORYREPO 与 GitHub App 已安装的访问权限不匹配,部署会失败并报 “Cannot access” 错误,因为它会通过预先克隆仓库来预热沙箱;你需要修复 App 安装或仓库取值,然后重新部署。
factory brain 是什么?在多次运行之间,Foreman 会保存关于你仓库的笔记,每次新运行都从这些笔记出发,从而随着时间积累上下文,而不是每个任务都从零开始。
能在不碰 GitHub 的情况下测试任务吗?可以,本地开发 TUI 让你在自己的机器上直接把任务交给 Foreman;产生的任何改动在进入 GitHub 之前仍会等待你的批准。
哪个环境变量控制触发流水线的 GitHub issue 标签?FACTORYLABEL,如果不设置,默认值为 “factory”。
Size
1.4 MB
Stars
1.2K
Updated
CommitSep 29
Age
2mo
Commits · 90 Days