Meet Foreman, an eve package mill that puts AI agents connected each shape of the improvement loop and keeps group connected the judgement calls.
Foreman takes tasks from GitHub and Linear, moves each 1 done 4 stations, and delivers a reviewed draught propulsion petition connected your repository. You review, people ready, and merge.
- Classifier triages the task: type, priority, complexity, actionable aliases not. When the task isn't actionable, Foreman asks the requester alternatively of building the incorrect thing.
- Analyst turns it into a scheme pinch acceptance criteria, moving from a unrecorded checkout of your repository.
- Implementer executes the scheme successful its ain sandbox, verifies pinch your repo's ain checks, and pushes a branch.
- Reviewer independently judges everything against the existent diff, pinch grounds for each verdict.
Each position is its ain supplier pinch its ain instructions, sandbox, and tools. The Reviewer sees only the pushed branch, ne'er the Implementer's reasoning. Between runs, Foreman keeps a factory brain: notes astir your repository that each tally starts from. See the pipeline and factory memory for the afloat picture.
- Label an rumor factory. The pipeline runs connected its own, posts advancement arsenic stations complete, and ends pinch a draught PR linked to the issue.
- @mention it connected an rumor aliases PR. Mentions from repo owners, members, and collaborators commencement an interactive session.
- Delegate successful Linear. Linear Agent Sessions tally the aforesaid pipeline and study advancement backmost successful Linear.
- The dev TUI. Hand it a task locally. Changes to GitHub hold for your approval.
- Red CI connected a mill PR. Foreman diagnoses the nonaccomplishment and pushes a hole to its ain branches, ne'er yours.
- Someone opens a propulsion request. Foreman posts 1 orienting remark for reviewers: a summary, not a review.
The Vercel deploy travel sets up everything: the GitHub connector, Linear connector, Vercel Blob store, and a punctual for the FACTORY_REPO and FACTORY_LABEL situation variables.
Configuration (see .env.example):
| FACTORY_REPO | Yes | — | The owner/repo the mill useful connected (the build fails without it) |
| FACTORY_SETUP_COMMAND | No | — | Runs erstwhile wrong the sandbox checkout astatine build clip (e.g. pnpm install), truthful each tally starts pinch limitations already installed |
| FACTORY_LABEL | No | factory | The rumor explanation that hands an rumor to the factory |
| FACTORY_BRANCH_PREFIX | No | factory/ | Branch prefix marking the factory's ain 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 erstwhile unset |
| GITHUB_CONNECTOR / LINEAR_CONNECTOR | Yes | — | Set automatically from Vercel Connect connector UIDs |
Link the task you deployed (or a caller one), propulsion its environment, and commencement the TUI:
Hand the supplier a task ("users study the password reset email arrives twice, hole it") and watch the 4 stations occurrence successful order, ending successful a draught PR connected FACTORY_REPO. Local runs are treated arsenic untrusted, truthful changes to GitHub hold for your support successful the TUI.
- Foreman Docs
- Vercel Connect
- eve Documentation
- GitHub Tools eve Extension
- eve Marketing Team
- eve Personal Agent
- eve Sanity Copilot
English (US) · 
Indonesian (ID) · 
