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)

linear
Searching Database…

1.2K ·GitHub
Eve-software-factory-template
What is this?Foreman is an 'eve Software Factory' that puts AI agents on every stage of the development loop while keeping humans in charge of judgment calls. It pulls tasks from GitHub and Linear, runs them through four agent stations, and delivers a reviewed draft pull request for you to merge.
Is this a chatbot or an automated agent pipeline?It's an automated multi-agent pipeline, not a chat assistant: a Classifier, Analyst, Implementer, and Reviewer each run as their own agent with their own sandbox and tools, though you can also interact with it via @mentions or a local TUI.
How do I deploy Foreman?Use the Vercel deploy flow, which sets up the GitHub connector, Linear connector, and a Vercel Blob store, and prompts you for the FACTORYREPO and FACTORYLABEL environment variables.
What do I need before deploying?You need an existing GitHub repository (owner/repo format) with the chosen GitHub App actually installed and granted access to it; Linear integration is optional for delegating tasks from Linear.
What's the main deploy pitfall?If FACTORYREPO and the GitHub App's installed access don't line up, the deployment fails with a 'Cannot access' error because it tries to prewarm sandboxes by cloning the repo up front; you need to fix the app install or the repo value and redeploy.
What is the factory brain?Between runs, Foreman keeps notes about your repository that every new run starts from, so it accumulates context over time instead of starting fresh each task.
Can I test a task without touching GitHub?Yes, the local dev TUI lets you hand Foreman a task directly on your machine; any resulting changes still wait for your approval before they reach GitHub.
Which environment variable controls the GitHub issue label that triggers the pipeline?FACTORYLABEL, which defaults to 'factory' if left unset.
What are similar projects?open-swe, claude-code-action, orca, grok-ship, pulls.review, github-mcp-server, factory, emdash
Which topics is it in?linear, pull-request, vercel, ci-cd, template, code-review, agent-framework, github, workflow-automation, ci, agent-orchestration, multi-agent
Creator
vercel-labs
Size
1.4 MB
Stars
1.2K
Updated
CommitSep 29
Age
2mo
Commits · 90 Days