Template name
Turn GitHub and Linear issues into reviewed draft pull requests with specialist eve agents and human approval before shipping.
eve Software Factory is a template for teams that want artificial intelligence agents to turn repository issues into reviewed draft pull requests. Its orchestrator, Foreman, assigns work to specialist agents and reports progress in GitHub or Linear. A person decides when to mark the result ready and merge it.
Start a run by labeling a GitHub issue factory, mentioning the bot on an issue or pull request, or delegating an issue in Linear. Foreman sends actionable work through four stations:
| Station | Work it performs |
|---|---|
| Classifier | Triages the request and identifies missing information. |
| Analyst | Builds a plan and acceptance criteria against a repository checkout. |
| Implementer | Writes code in a sandbox, runs the repository's checks, and pushes a branch. |
| Reviewer | Evaluates the pushed branch against the acceptance criteria, using a different model vendor from the implementer. |
Each station has its own instructions, sandbox, and tools. The reviewer receives the branch without the implementer's reasoning. Foreman's instructions allow up to two revision cycles; if review still fails, they direct it to report the unresolved findings without opening a pull request.
After approval from the reviewer, Foreman opens a draft pull request. It can also diagnose failed CI on branches with the configured factory prefix and push a repair. That repair workflow is instructed to stop after two attempts and ask for human troubleshooting.
Use this template to move an issue through planning and independent review before your team receives a pull request. It supplies specialist handoffs and policies for unattended work.
Adapt station instructions and models to build AI agents around your development process. To choose the best AI agent workflow, examine what the reviewer sees and where human approval is required. Foreman gives you a concrete starting point for both, with included evaluations for routing, safety, and prompt-injection behavior.
eve is an open-source AI agent framework with durable execution and declared subagents. The factory implementation assigns stations to subagents with Vercel Sandbox execution environments.
Vercel Connect supplies GitHub and Linear credentials. Git credentials are injected at the sandbox firewall without entering its processes. Vercel Blob stores shared repository notes, while Blob and model access authenticate with the project's OIDC token.
Set FACTORY_REPO to an existing repository in owner/repo format and give the selected GitHub App access to it. The repository setup guide covers the GitHub and Linear connectors, Blob storage, and configuration. Keep the factory branch prefix reserved for factory work because it determines which branches qualify for automated CI repair.
Unattended runs stop at draft pull requests. Attended requests to mark a pull request ready require human approval, and merging is absent from the supplied tools. The push tool refuses main and master; review that protection if your default branch has another name. Approval requests appear in GitHub comments, Linear, or the development TUI.
The optional full-pipeline evaluation pushes a real branch. Use a scratch repository when running it.
Apply the configured factory label to a GitHub issue, mention the bot in an issue or pull request, or delegate work in Linear. GitHub label intake requires at least triage permission, and mentions are accepted from repository owners, members, and collaborators. If classification finds missing information, Foreman asks for clarification before implementation.
The classifier, analyst, implementer, and reviewer have distinct instructions and execution environments. The reviewer checks the actual branch against the plan's criteria without seeing the implementer's reasoning. Its model comes from a different vendor than the implementation model.
No. The supplied GitHub tool list excludes merging. An unattended run can produce a draft PR, while marking it ready in an attended session waits for a person's approval. A person performs the merge.
The automated repair trigger accepts failed check suites on pull requests whose head branch matches the configured factory prefix. Its instructions limit repairs to two attempts before handing the problem to a person. The branch prefix determines eligibility, so reserve it for factory work.
Shared notes in Vercel Blob hold build quirks and verification details, including recurring review findings. Foreman reads them at the start of a task. Unattended runs cannot update this memory; trusted attended sessions can write it, and writes from the development TUI require approval.

Coordinate a marketing lead and five specialist agents in Slack, with Notion drafts, Typefully posts, and Resend email campaigns.

Build a personal eve assistant with persistent web chat, linked Slack identity, optional iMessage, and per-user memory.

Maintain GitHub from your inbox with Kody: weekly issue digests, actions by email reply, pull request summaries, and Linear work.
