Every system in this series—the thermal-battery furnace hack, the private CFO, the local fitness coach—runs on a standard M2 Mac Mini with 8GB of RAM.
Not a $4,000 Mac Studio. Not a rack of GPUs. Just the baseline Mac Mini sitting right on my desk.
My monthly operational cost is exactly $40: a $20/month Google AI Pro plan and a $20/month ChatGPT Plus subscription. No metered API bills. No surprise credit card charges at the end of the month.
You don’t need an enterprise cloud budget to build autonomous agents that do real work in the physical world. You just need to stop routing every simple request to the most expensive model on the market.
Want the exact prompt brief, routing flow diagram, and memory management setup? Read Build Notes: Multi-Model on Cheap Hardware.
How the agent bootstrapped its own environment
I didn’t manually configure the multi-model architecture. I described the goals—low cost, data privacy, and automated code review—and my primary agent, antigravity-cli, built the environment itself.
The agent executed three setup tasks:
- Installed Ollama: Set up the local model runtime on the Mac Mini to execute lightweight open-source models on CPU/unified memory.
- Configured Model Context Protocol (MCP): Wired up MCP tool bindings so the main agent could hand off specialized tasks to other LLM runtimes automatically.
- Established Adversarial Review: Configured a secondary CLI reviewer agent to audit code before execution.
I approved terminal steps and watched it build its own toolchain. Now, whenever I launch a project, a dedicated setup subagent handles environment provisioning automatically.
The 3-tier multi-model orchestration model
Rather than relying on a single mega-model, the stack routes tasks across three distinct tiers based on cost, speed, and privacy:
1. Heavy Cloud Reasoning (Architecture & Code Generation)
Complex logic—like generating ESP32 furnace firmware, writing BigQuery SQL schemas, or analyzing financial projections—gets routed to frontier cloud reasoning models (Gemini / GPT-4o). That’s what the $40 in consumer subscriptions is for, and I use it where deep reasoning matters.
2. Adversarial Review (The Skeptic Agent)
Trusting a single LLM to audit its own code is a recipe for silent failure. Models are notoriously bad at catching their own mistakes. Before any generated code runs against my furnace board or financial database, the primary agent hands the draft to a different model family operating as an adversarial reviewer. Two models from different lineages reviewing each other catch edge cases, syntax bugs, and logic flaws that a single model sails past.
3. Local Open-Source Execution (Privacy & Zero-Cost Grunt Work)
An 8GB Mac Mini can’t run a 70B parameter model, but it handles a 4B parameter open-source model (like Qwen via Ollama) effortlessly. Routine, high-volume tasks—scrubbing bank statement text, parsing voice logs from the gym, and formatting local Markdown files—run 100% locally.
This local tier delivers three immediate wins:
- Private: Sensitive text never leaves the Mac Mini.
- Free: Zero API token metering.
- Fast: No network latency or cloud API round-trips.
The enterprise takeaway
The default instinct in most enterprise IT departments is choosing a single frontier model, pointing every internal workload at it, and acting surprised when the cloud invoice arrives.
That isn’t an AI strategy—it’s a single point of failure with an uncapped meter.
Real value comes from orchestration. Match the workload to the cheapest model that can reliably execute it: heavy reasoning to frontier cloud models, code auditing to a secondary reviewer, and sensitive data processing to local open-source models.
Do that, and a $500 machine sitting right on your desk running on $40 a month will outwork an enterprise setup costing a hundred times as much.
Want the exact prompt brief, routing flow diagram, and memory management setup? Read Build Notes: Multi-Model on Cheap Hardware.
Comments welcomed: