Linux Colorado
  • Contact
  • Search
  • Topics
  • About
  • Post

Post

November 6, 2026

I Gave a Three-Cent Coding Agent a Desk in the Homelab and Made Claude Its Reviewer

Claude Code is a great senior engineer and a terrible use of money for “add a test for row 144.” That one task doesn’t need judgment; it needs a person (or a cog) who will read the spec, write the test, run the suite, and report back honestly. Paying Opus-level tokens for that is like chartering a helicopter to cross the creek.

So I hired a cheaper junior. A DeepSeek-backed agent runs in a container on the homelab’s GPU box, paid per job instead of per month, briefed in writing, and — this is the whole trick — with Claude kept for the one part that actually needs a senior: reviewing its work. Claude reviews; I merge. About twenty jobs in, the agent’s bill has not dented a ten-dollar OpenRouter credit, and the process has taught me more about my own briefs than about the agent.

read more
November 5, 2026

Forty Cents of Agent Research, One Hallucinated Email, and the Script That Caught It

NeonBench is in public beta, and the people most likely to care are the schools and studios that still teach glass bending. There is no directory of them, and finding them is tedious web research, which is exactly what a cheap agent is for, and exactly where a cheap agent will make things up. So I spent forty cents on ten agent jobs, got back a spreadsheet of trade schools, and built a deterministic verifier that refused to trust any of them. It caught a hallucinated email address. The whole thing is the subject of this post.

The agent is the same Hermes/DeepSeek setup I use for code jobs on the homelab GPU box (.62): an open-source agent framework in a container, a DeepSeek V4 Flash model through OpenRouter, briefs written as Markdown files, one job per brief, run in parallel. For research jobs it gets the web, file and terminal toolsets and a plain output directory instead of a git worktree. A pleasant surprise: the framework’s web search works with no API key at all (it falls back to a free search backend), so the research side cost nothing beyond model tokens.

The punchline, spoiled up front: the model followed every rule except the one that mattered, a dumb script was the only thing that noticed, and the forty cents bought a lesson about rules versus controls that I’d happily have paid more for.

read more
November 4, 2026

Web Form to CRM in Two Seconds: Wiring Wix, n8n, Mailgun and Odoo 18 (and a Bug That Hid for Seven Weeks)

I am a one-person consultancy. One of my clients is a sign shop whose quotes, leads and invoices live in a single self-hosted Odoo 18 instance on a small VPS, which is the source of truth for both my company and theirs as two companies in one database. The automation glue is n8n (2.x, Postgres 17, pinned images) in Docker on the homelab AI box .62, reachable from the internet only through a Cloudflare Tunnel on a dedicated webhooks hostname. Outgoing mail goes through Mailgun; pushes land on my phone through ntfy.

This post is not a tutorial on any one product. It is the plumbing between them, and it is three bugs that each took a real lead or a real week to surface: a DMARC policy that bounced the very first email about a new lead, an inbound-mail route that would have silently eaten every reply, and an n8n trap I want to tattoo somewhere, where a scheduled job failed every morning for seven weeks while the identical workflow passed every time I ran it by hand.

Everything here is exported into an infra-as-code repo, in the spirit of my earlier write-up on backing up a homelab as code, so none of this is a story about remembering how it was set up. It is the story of what the plumbing does, and the three places it quietly broke.

read more
  • ««
  • «
  • 1
  • 2
  • 3
  • 4
  • 5
  • »
  • »»
© Linux Colorado 2026