Self-Host Software Factory

Foreman, an open-source software factory from eve, deploys AI agents across four pipeline stations—Classifier, Analyst, Implementer, and Reviewer—to turn GitHub and Linear tasks into reviewed draft pull requests while keeping humans on judgment calls. The Vercel deploy flow requires a valid FACTORY_REPO in owner/repo format and a GitHub App with access to that repository, or the deployment fails with a 'Cannot access <owner/repo>' error. Foreman supports issue labels, @mentions, Linear delegation, a developer TUI, automated CI fixes on its own branches, and orienting comments on external PRs.

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. Classifier triages the task: type, priority, complexity, actionable or not. When the task isn't actionable, Foreman asks the requester instead of building the wrong thing. Analyst turns it into a plan with acceptance criteria, working from a live checkout of your repository. Implementer executes the plan in its own sandbox, verifies with your repo's own checks, and pushes a branch. Reviewer independently judges everything against the real diff, with evidence for each verdict. 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 https://ask-foreman.dev/docs/pipeline and factory memory https://ask-foreman.dev/docs/memory for the full picture. Label an issue The pipeline runs on its own, posts progress as stations complete, and ends with a draft PR linked to the issue. factory . @mention it on an issue or PR. Mentions from repo owners, members, and collaborators start an interactive session. Delegate in Linear. Linear Agent Sessions run the same pipeline and report progress back in Linear. The dev TUI. Hand it a task locally. Changes to GitHub wait for your approval. Red CI on a factory PR. Foreman diagnoses the failure and pushes a fix to its own branches, never yours. Someone opens a pull request. Foreman posts one orienting comment for reviewers: a summary, not a review. 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 | 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.