FarmFactory
A free web app for seeing every farm you own in one place - progress at a glance, shared checklists, and a live connection to the Operator skill.
What It Is
Farmwork lives inside a repo, and the Operator sweeps repos from your terminal. FarmFactory is the same picture in a browser - every farm you own as a row, its health score, its checklist progress, and the Farmwork documents it has synced.
It reads the _AUDIT/ documents your farms already generate, so there's nothing extra to maintain. A farm that runs /audit shows up in FarmFactory with a current score without you doing anything else.
Core Principle
FarmFactory doesn't own your work - your repos do. It reads what Farmwork already writes and gives you somewhere to look at it that isn't a terminal. Delete your account tomorrow and every farm still works exactly the same.
Why Use It
The terminal sweep is fast but private and momentary. FarmFactory is useful when you need the state to be shared or durable:
- Someone else needs to see it. A teammate or client can look at a farm's progress without cloning anything or running a CLI.
- Progress should persist. Checklist completions live server-side, so they survive a fresh clone, a new machine, or a different agent.
- You want it visual. Sorting a dozen farms by score, or grouping them, is easier in a table than in scrollback.
- You want an embed. Farms can be shared read-only via a token URL, useful for a status page.
If none of those apply, the Operator alone is enough - the git sweep works with no account and no network.
Checklists
A checklist is the standard you hold every farm to - the things a project should have before you'd call it done. Items are defined once, centrally, grouped by theme, and every farm is measured against the same catalog.
Each item on a given farm is in one of three states:
- Completed - done on this farm, counts toward the percentage
- Skipped - doesn't apply here, and drops out of the denominator entirely
- Pending - still outstanding
Why skipping matters
A static site doesn't need a database migration policy. Without skipping, that item would sit unchecked forever and the farm could never reach 100% - so the number would stop meaning anything and you'd stop looking at it. Skipping keeps the percentage honest: it measures what's actually in scope for that farm.
Operator Connection
FarmFactory exposes a JSON API, and the Operator speaks it. Once connected, checklist progress appears in your terminal sweep alongside git state, and you can complete items without opening a browser:
$ operator checklist DoTheseTasks
DoTheseTasks ████████░░ 81% (#7)
14 done, 2 skipped, of 19 items
Infra
[x] 12 Set up CI
[ ] 13 Add a staging environment
Docs
[-] 18 API reference (skipped)
$ operator complete DoTheseTasks 13
Completed 1 item(s) — now 87% (15/17)Writes go through the same API the web UI uses, so a completion from your terminal shows up for anyone looking at the browser, and the other way around.
Safe for agents to drive
The checklist endpoints are idempotent - they set state rather than toggling it. Completing an already-completed item leaves it completed. That matters when an AI agent is making the calls: a retried request can never silently undo work that was already done.
Getting Set Up
FarmFactory lives at factory.farmwork.dev. Sign in, add your repos, then connect the Operator with an API key:
- In FarmFactory, go to Admin → API Keys and create a key
- Put it in
~/.operator/config.json, or export it - environment variables win, so you can keep the key out of the file entirely
export FARMFACTORY_URL="https://factory.farmwork.dev"
export FARMFACTORY_API_KEY="…"
operator checklists # confirm the connectionDon't have the Operator yet? It installs from the Farmwork repo in one command - see The Operator.
The connection is optional
Skip all of this and the Operator still sweeps git across every farm. You'd only lose the checklist column. Nothing about Farmwork itself requires an account.
The Wynter.ai Suite
FarmFactory is part of Wynter.ai, a set of tools for building software with AI agents. It's free to use for managing your farms.
The pieces are designed to be taken separately. Farmwork is MIT-licensed and works on its own; the Operator works with or without FarmFactory; FarmFactory reads what your repos already contain. Adopt whichever layer is useful and ignore the rest.