Issues in, pull requests out
Label an issue factory or comment /factory. Only logins on the policy’s allowed list can start work. Everyone else’s text is recorded and never acted on.
Lumbridge Build
Gated · opens on November 13, 2026Lumbridge Factory Agents build. People merge.
Lumbridge Factory turns an issue into a pull request. A coding agent builds the change in a sandbox on its own branch, and nothing is ready until CI passes on that exact commit and a second agent has reviewed it. Then a person merges. It is for teams that want agents working through a backlog without giving them the keys to main.
Tour
See Factory at work.
The factory2 command
One ticket, and the policy it ran under.
show prints a ticket's branch, budget and turns. policy prints who may ask for work, the required checks and who merges. Shown in both themes.
01 · What it does
What Factory does today.
Two gates plus current main
A change is ready only when every required check is green on the head commit, a reviewer has passed that same commit, and the branch contains today’s main. A new commit starts the gates again.
A repair loop
A red check or a changes_requested review wakes the same builder session with the failing log or the findings. After three review rounds it stops and asks a person.
A sandboxed builder
Agents run as their own unix user behind a default-deny network allowlist. They hold no code host token. Their git key can push only factory/* branches, and a hook refuses reads of secrets.
Recovery, not quarantine
Kill either daemon or reboot the host. A turn still running is reattached, a finished one is collected, and a cut-off one resumes the same session with a recovery note. No comment is posted twice.
Budgets and capacity
Each ticket has a token budget and a wall-clock budget. Reaching one asks a person; it does not kill the work. Slots are held only while a turn runs, and account limits make turns wait, not fail.
02 · How it works
Two daemons, three unix users, one store.
The part that decides and the part that runs agent code are separate processes under separate users. Neither can read the other’s secrets.
- 2.1
factoryd, the engine
Polls the code host, makes tickets, schedules turns, reads the gates and posts comments. It is the only writer of a SQLite store. Every outside effect is stored first and carried out after commit with an idempotency key.
- 2.2
agentd, the endpoint
Prepares a git worktree per ticket and runs each agent turn as a fresh headless process. It keeps no ticket state. factoryd talks to it over one unix socket, and only factoryd’s user may connect.
- 2.3
Builder and reviewer
The builder reports through a small MCP tool server:
report,reply,handback,recall. Its word is a claim that factoryd re-checks. The reviewer is a different session in a read-only worktree pinned to the commit. - 2.4
The policy
One document names who may ask, each repository with its required checks and CI runner, data rules, outside-action rules, the merge policy, slots and budgets. factoryd refuses to start if a part is undecided.
03 · Use it
Run the two daemons, then watch tickets.
Each daemon reads one JSON config. The policy is installed from factoryd.json on a new store and changed afterwards with factory2 policy.
# as the factory user, then as the control user
python3 -m factory2.agentd --config /etc/factory2/acme/agentd.json
python3 -m factory2.factoryd --config /etc/factory2/acme/factoryd.json
export FACTORY2_DB=/var/lib/acme-control/factory.sqlite3
factory2 policy add-repo acme/api --runner acme-ci --check "CI / checks (pull_request)"
factory2 policy allow gitea dana
factory2 policy slots 2
factory2 status
factory2 tickets --all
factory2 show t-ccd41800
factory2 hold t-ccd41800 --release
factory2 --json status
04 · Docs
The Factory manual.
These pages are in the repository and open with it. Until then, the Guide covers the same ground and is readable now.
- 01
Design
The domain model, a ticket’s life from accept to merge, the three gates, capacity, reliability and the security rules.
- 02
agentd
Its config file, how a turn stops, the tool hook, and a plain list of what the hook cannot stop.
- 03
factoryd and agentd protocol
The socket, every operation, turn idempotency, session ids and the eight turn outcomes.
- 04
Policy and configuration
The
factoryd.jsonandagentd.jsonkeys, with two complete instance examples ininstances/. - 05
Installing an instance
Step-by-step install logs with an undo beside every step: users, egress, bots, branch rules, CI runner and units.
- 06
Verifying the boundary
Scripts that prove what each user can reach and that the bot cannot push or merge main.
Read the Guide chapter: Factory and modelsRequest access to the repository
05 · Works with
One part of one system.
- Lumbridge MobileApproving an issue card on the phone files it with the
factorylabel, and that starts a ticket. - Lumbridge CoreThe Core repo is in our own factory’s policy. Its CI script and data rules are in
instances/. - Lumbridge AppThe App repo is in the same policy. Its tests use throwaway homes and scratch cores only.
Not yet
- It is Python today (standard library only, SQLite). It is not Rust yet.
- Gitea is the only code host. GitHub is not supported yet.
- No installer. A new instance is host scripts and an install log you adapt by hand.
- The watchdog and the model-based router are designed, not built. Work starts only from an explicit request.
Questions
Questions about Factory.
Why is the command called factory2?
It is the second version of the factory, and the command, its modules and its config paths still carry that name. The product and the repository are Lumbridge Factory. A lumbridge-factory command will replace it; until then the commands on this page are the real ones.
Which agents and models does it drive?
Claude Code today, headless, one process per turn. Builder and reviewer models are set in the policy with builder_model and reviewer_model. A Codex adapter is in the tree, but it is off by default and has not run a real turn.
What stops an agent pushing to main?
Three layers. A server-side pre-receive hook lets the factory’s bot push only factory/* branches and no tags. The branch rule on main has a merge whitelist of people. A tool hook on the agent refuses the obvious attempts before they run.
What happens when a job fails?
A red check goes back to the same builder with the log tail. A transient error is retried three times. A cut-off turn resumes with a recovery note, and five cut-offs in a row become one question to a person. A ticket never hangs silently.
Which code hosts does it support?
Gitea, including Gitea Actions for CI. The source, the comment channel and the gate reads sit behind interfaces, but only the Gitea ones are written.
What is the license, and when can I read the code?
Apache-2.0. The repository opens on November 13, 2026.
Want Factory running for your team?
Self-host it, or talk to us about setting it up with you.