Garlic Farmer Builds 19K-Line AI Agent System on Android Phone

Development Environment and System
A garlic farmer from Gyeongsang province, South Korea, has developed an AI agent system called "garlic-agent" using only an Android phone with Termux terminal app. The system consists of 19,260 lines of Python code (as verified by asking multiple AIs to count it) and runs complex automation scripts in a custom programming language.
The system rotates between multiple AI providers including Gemini, Groq, and NVIDIA, saves context in SQLite, and runs entirely on a mobile device. The farmer describes it as a "personal project in AI era" developed without a PC.
Workflow Methodology
The entire development process revolves around manual copy-paste operations. The workflow follows this pattern:
- Ask Claude to "diagnose project health"
- Claude generates a diagnostic script
- Copy the script manually (press and hold with finger)
- Switch to Termux, paste, and execute
- Copy the results
- Switch back to Claude, paste results for analysis
- Claude generates patch scripts
- Repeat the copy-paste-execute cycle
The farmer reports performing this cycle "thousands of times a day" and has maintained this workflow through "tens of thousands of conversations" with AI systems.
AI Role Division
The system uses three primary AI roles:
- External analysis - Claude: Diagnoses code from outside the project, generates diagnostic scripts, but cannot execute code directly. Requires manual intervention to run scripts in Termux.
- Internal execution - Gemini: Runs as an API AI inside garlic-agent, reads files, executes commands, and returns results. Has internal knowledge of the codebase from daily operation.
- Human connector: The farmer acts as middleware between Claude (in web browser) and Gemini (in Termux), carrying results between both sides, delivering questions, and making decisions when AI judgments conflict.
Context Management
To manage multiple AI sessions, the farmer assigns alias-like numbers at the end of each response (e.g., analysis21, analysis22, analysis23). This helps distinguish between different AI instances when managing dozens of chat windows. When one AI leaves a record in CHANGELOG, the next AI reads it and takes over, creating context consistency.
The handover record has grown to 10,730 lines over approximately a month and a half of operation. The farmer emphasizes that this level of context management is "impossible to explain" and recommends experiencing it firsthand.
Practical Implementation
The system runs continuously - the farmer returns from garlic fields, turns on the phone screen, and continues from where they stopped. Development happens during breaks while digging garlic and after lunch. The farmer notes that while AI remembers context (eliminating the need for human memory), the process requires "very much human touch every moment."
The farmer explicitly states they don't trust AI alone: "I only trust my instinct and gut feeling. Autonomous AI agent? I dare say. Precise work is still far away. I am not making this system to plan travel schedule."
📖 Read the full source: r/ClaudeAI
👀 See Also

One prompt that finds, emails, and logs 200 investor contacts via Claude Code
A single prompt for Claude Code or any AI agent scrapes investors, checks duplicates in Gmail/Notion, sends personalized cold emails via SMTP, and logs everything to Notion — all autonomously.

Mesh Architecture for AI Agents: Client Isolation and Cross-Project Coordination
A developer running a micro-agency describes a mesh architecture where each client gets specialized AI agents that communicate via markdown files, enabling domain expertise, cross-project coordination, and client isolation across 44 projects and 14 organizations.

One Month with OpenClaw: Personalization Successes and Stability Challenges
An AI researcher replaced ChatGPT Plus with OpenClaw for one month, achieving personalized chatbot functionality through USER.md and PERSONAL_MODEL.md files, daily check-in agents, and spending reports, but encountered persistent breakage requiring Claude Code intervention.

Using Kimi K2.6 to Properly Uninstall macOS Apps by Finding Hidden App Directories
A developer describes using Kimi K2.6 to automatically find and delete macOS app directories, including hidden ~/.appname and ~/Library/Application Support files, with a custom agent that edits its base knowledge to improve the process.