Who it is forA developer away from their desk who wants to send a change or check on progress from a phone.
The problemStarting and checking agent work usually means being at a terminal on the machine that runs it.
The outcomeYou ask for work in the Claude app and the farm starts it, and you can see every sub-agent in the farm UI.
What you need first
- Docker on a machine or server that stays on
- A Claude subscription to sign in with
- A Git repo you control, with a deploy key if you want the farm to clone and push to it
- Your test command, for example pytest -q
Steps
- Install and start the farm with the one-line installer, then log in.
- Open the Claude app on your phone and go to Code.
- Select [Clodfarm] Clodfarm.
- Ask for the work in plain words, for example "add CSV export to the report page".
- Open http://localhost:8080 to watch the sub-agents on the farm.
Prompt for your agent
Install clodfarm from github.com/matank001/clodfarm with the one-line install script, then open the farm UI at http://localhost:8080. Send the task <task description> from the Claude app under Code, then confirm the new sub-agent appears in the farm UI and report its status.
Caveat. The phone view reaches the farm only where it is running, so the host machine must stay on and reachable.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page