by matank001
clodfarm (say it out loud): a farm of Claude Code agents. Plant a mission, they split it into sub-agents, open the work, and pace themselves on each account's real 5-hour and weekly usage. Steer it from the Claude app.
# Add to your Claude Code skills
git clone https://github.com/matank001/clodfarmSee how clodfarm compares with popular alternatives.
clodfarm is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by matank001. clodfarm (say it out loud): a farm of Claude Code agents. Plant a mission, they split it into sub-agents, open the work, and pace themselves on each account's real 5-hour and weekly usage. Steer it from the Claude app. It has 62 GitHub stars.
clodfarm's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/matank001/clodfarm" and add it to your Claude Code skills directory (see the Installation section above).
clodfarm is primarily written in Python. It is open-source under matank001 on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh clodfarm against similar tools.
No comments yet. Be the first to share your thoughts!
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
clodfarm (say it out loud) is a farm of Claude Code agents running around the clock in a container. A clod is a lump of soil, and this is where your agents grow.
A while true; claude -p loop forgets what it did, can't split work, can't be reached from your phone, and burns
through your limits. clodfarm is the operations layer it's missing:
| Always on | Crashes, restarts and timeouts don't lose work. Claudes come back and pick up where they left off. |
| Talk to it from your phone | Every Claude is a session in your Claude app. Ask for work from anywhere. |
| Sub-agents you can see | Big jobs split into sub-agents, each on its own branch, and you watch them work. |
| Never eats your week | Paced on your real 5-hour and weekly usage. It leaves you 20% and never pays overage. |
| Claudes that work together | Teammates' Claudes message each other and run work on whoever has budget left. |
| Nothing lands untested | Work reaches main only when your tests pass. |
| Schedules | "Every weekday at 9, triage new issues." Cron, intervals or one-offs. |
| Dashboards | The Claudes keep live pages that show what is improving (docs). |
| A browser, logged in | Log in to a site once in the farm's browser (LinkedIn, an admin panel) and every Claude works there as you, in the window you watch (docs). |
| Slack | DM or @mention the farm and a sub-agent answers in the thread. Two-minute setup (docs). |
| Claude Code on your laptop | Connect over MCP and hand the farm work without leaving your editor. |
| Builds apps on AWS (optional) | The Claudes ship their own serverless apps inside a fenced role with a hard budget cap (details). |
| Many boxes, many seats | One farm and one repo across machines and accounts, each on its own budget. |
| Tells you when it matters | Failures and usage limits go to ntfy, Slack or Discord. |
| A farm you can watch | Every Claude, its sub-agents, usage and tools at a glance, in your browser. |
You talk to your Claude in the Claude app; the farm UI shows who is working on what; the Claudes and you use the same CLI.
One container, no config, no database to run:
curl -fsSL https://raw.githubusercontent.com/matank001/clodfarm/main/scripts/install.sh | sh
It pulls the image, starts clodfarm (restarting on reboot), and opens the login: a URL you approve on any
device, then paste the code back. Then open Claude app → Code → [clodfarm] clodfarm on your phone and just talk to it:
"add CSV export to the report page", "have gil's Claude review it", "every morning at 9, triage new issues".
Or from a shell:
docker exec clodfarm clodfarm spawn "Add CSV export" --prompt "Add CSV export to the report page, with tests."
docker exec clodfarm clodfarm status
The farm UI is at http://localhost:8080
(see docs/ui.md): the password is printed once in docker logs clodfarm, or set FARM_UI_PASSWORD.
From the UI you can also log the farm in: tap the egg, open the Claude login link and paste the code back.
docker run -d --name clodfarm --restart unless-stopped \
-v clodfarm_claude-home:/home/farm/.claude -v clodfarm_workspace:/workspace \
ghcr.io/matank001/clodfarm
docker exec -it clodfarm clodfarm login
Or clone the repo and run docker compose up -d. A .env is optional: copy .env.example to change any setting.
Either way the farm's state lives in a SQLite file inside the workspace volume, so there's nothing else to run.
[!TIP] Point it at a real repo with
FARM_REPO_URL(plus a deploy key) and setFARM_VERIFY_CMD="pytest -q". The farm clones the repo, and every sub-agent's work lands onmainonly when your tests pass.
The farm is a remote MCP server, so the Claude Code on your laptop can see the farm, start sub-agents on it and message its Claudes:
claude mcp add --transport http --scope user farm http://localhost:8080/mcp # or https://<your farm>/mcp
Run /mcp in Claude Code and sign in. The farm's own page asks for its password and a name for your computer, and
Claude Code gets a token for this farm only (OAuth 2.1 + PKCE; clodfarm disconnect ends it). Then just ask:
"what's the farm doing?", "have the farm add CSV export, on gil", "tell noa the release is out".
See docs/mcp.md.
| What you get | |
|---|---|
| Single deployment | One box, one Claude account. Everything in one container. |
| Multiple deployments, one farm | Several boxes on your account or teammates' own accounts: one farm and one repo, each account paced on its own budget. |
| + Apps role (optional) | Add-on for either one: the Claudes create and run their own serverless apps on AWS, fenced by a permissions boundary and a monthly budget. |
You can start single and add boxes later. A new box simply joins the first one's table.
**Any Doc