Clodfarm runs a team of Claude Code agents from your phone, paces each account to its real usage limit, and adds Stripe, AWS and Google Ads

A Claude Code session on your laptop stops when you close the lid, and a while true; claude -p loop forgets what it did the moment it restarts. Clodfarm is a new open-source project that keeps a team of Claude Code agents running in a container, one per person on the team, and lets you steer any of them from your phone.

The repository at matank001/clodfarm was created on 25 September 2026 and reached 92 stars, 42 forks and an MIT licence in the five days that followed, per the GitHub API on 30 September. It is written in Python and ships as one Docker image.

What lives on the farm

Each teammate connects their own Claude subscription. That account becomes a Claude on the farm with its own plot on the UI, its own 5-hour usage window and its own weekly limit. The maintainer, who goes by matank on the repository, measures those limits the moment an account joins and keeps them current: when a Claude nears 80 percent of its weekly cap, it pauses instead of paying overage. Big jobs split into sub-agents on their own git branches, and a sub-agent from one Claude can run on a teammate's account when their own is out of budget.

You talk to your Claude in the Claude app on your phone, using the "Code" mode. Ask "add CSV export to the report page" and the farm picks it up. Ask "have gil's Claude review it" and a sub-agent runs on gil's account. Ask "every weekday at 9, triage new issues" and the farm keeps a schedule. The farm UI at http://localhost:8080 shows every Claude at its plot with its own live terminal, tokens burned per Claude and across the whole farm, and a queue of approvals waiting on a person.

What the farm can reach

The pitch on the repository is that the farm is set up to build and sell a product on its own. Three connectors ship with it: an AWS role with a hard monthly budget cap for deploying serverless landing pages and small SaaS backends, a Stripe connection that lets any Claude create products, prices and payment links and send invoices, and a Google Ads connection that lets the Claudes report on spend, clicks and conversions and change budgets, bids and campaigns. The Claudes only charge, refund or raise a budget when a person asks, and Stripe can start in test mode.

Two more pieces are there for teams that want a mixed setup. A remote MCP server lets Claude Code on your laptop see the farm and start work on it without leaving your editor. And bots on free or local models, through OpenRouter or Ollama, can take the well-specified jobs your paid Claudes send them, so the farm keeps working when everybody's Claude subscription is paced. Work reaches main only when a project-defined test command passes.

Nothing here was independently tested. The traction is real (92 stars in five days, 42 forks, 18 contributors on the fork graph, verified 30 September through the GitHub API) and the maintainer states the project is early. For a team that already runs several Claude Code seats and finds itself watching every terminal, the farm is a place to see them side by side and keep any one account from eating its own week.

Source

• GitHub repository, primary source: https://github.com/matank001/clodfarm
• GitHub REST API for star and fork counts, queried 30 September 2026: https://api.github.com/repos/matank001/clodfarm