It asks what you want
Create a repository and an intake session opens. It reads what is there, asks you what to build, and writes the plan from an empty repository to the finished product, one item per step.
// idea · backlog · design · code · shipped
A farm does more than write code. It helps you turn an idea into a backlog it can work, settles the design with you before the first screen, runs on machines you own, and comes with the tools a real app needs.
runs onyour hardware
leaves the housethe ai · git
with a local model100% local
in the boxsound · 3d
Unattended work is only as good as the list it works from. The farm helps you write that list: small items, each with a finish line it can check, in the order they can be built.
Create a repository and an intake session opens. It reads what is there, asks you what to build, and writes the plan from an empty repository to the finished product, one item per step.
One deliverable per item, with a line saying how the farm can check it is done, the host it needs and the items it waits for. What only a person can do — a store account, a signature — becomes an item of its own, so nothing hides inside another.
An empty backlog opens a steward session: it sums up what was done and asks what you want next. Your answer, in plain words, becomes new items. Any session that finds more work files it too.
.farm/backlog/0042-sign-in-with-apple.md
- [ ] #42 Sign in with Apple on the account screen
accept: a new user signs in with Apple on iPhone and Mac; the account
screen shows their name; the UI tests cover both
host: mac
needs: 38
effort: mediumBefore anything is built, a design session can settle what your app looks like — with you, not for you. Design here means the look; the architecture is worked out separately, in the intake session that starts a project.
A handful of questions, then a proposal, then rounds until you approve it. Silence or a passing "ok" is not approval — the session waits for a real yes.
A DESIGN.md with the palette and the role of every colour, the type, the spacing and the components, plus mockups of the two to four screens that matter most.
Ask for the design first and the lanes wait until you approve it. From then on every screen they build uses its tokens and matches its mockups, and only a design session may change it.
The farm is software you install, not a service you send your code to. Everything it does happens on your machines. Two things leave them — the AI and your git host — and both can be brought home too.
stays on your machines
leaves them
The AI session talks to the provider you chose, on your own subscription or key — unless you run a local model.
GitLab, GitHub or Azure DevOps — or point it at your own server, or keep a project with no remote at all.
A question from a blocked item reaches your phone through Apple’s push service.
The farm runs OpenCode with a model on your own GPU. Pair it with your own git server, or a project with no remote, and the whole farm — planning, coding, testing, landing — runs without the internet. A few extras, like remote control from your phone, work only with Claude.
An app needs more than code. Every host comes with generators for sound and 3D models, written as code so they can be reviewed, rebuilt and versioned like the rest — and every session is told they are there.
Sound effects written as code — taps, pickups, hits, explosions, engines, seamless loops and ambience — rendered to 48 kHz WAVs with a manifest. The same id always gives the same sound, and about 240 example sounds come with it.
Low-poly 3D models written as code and exported as GLB, for Unity, three.js, SceneKit and RealityKit. Each one is checked, rendered, and shown in a web viewer with its moving parts animated.
A sound or a model one project makes can be shared with every project on the farm in one command. A project’s own version always wins over the shared one.
Step-by-step recipes the sessions follow for jobs every app meets: AdMob ads with EEA consent in an iOS app, proven in a shipped game, and a TestFlight upload coming soon.
Linux, Mac and Windows machines, side by side. Each host says what it can build, and items wait for the one that can: Xcode work for the Mac, installers for Windows. The farm installs Unity (without the Unity Hub) and the Swift, Node, Go and ESP32 toolchains itself.
A stuck item asks you a question with the answers to pick from. One tap on your phone frees every item blocked the same way, and the work resumes.
The farm sends you a summary every day, comparing this week with the last, so a day without one tells you something is wrong.
Every item is tested again on the machine before it is pushed. A change that fails never reaches main.