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.
Teaching an AI to Develop My RAW Photos: A Self-Hosted Linux Pipeline
I wanted to answer a specific question: could an AI agent do the boring, careful parts of my photography workflow — the parts I actually skip because they take too long?
Not “make my photos look good” in the Instagram-filter sense. I mean the tedious, correct-but-thankless work: pulling the right RAW off my server, applying the exact lens-correction data for the exact lens I used, denoising only the frames that need it, keeping the EXIF intact, filing everything under the right date, and getting a print onto photo paper without fighting a driver. The stuff a careful darkroom tech would do and a busy human never quite gets around to.
So I built it. A local, self-hosted pipeline where Claude Code can reach into my Immich library, pull original Canon CR3 RAW files, develop them in darktable with camera- and lens-specific corrections, retouch in GIMP, print on a networked Canon photo printer, and push finished JPEGs back into Immich as new assets — all driven through the Model Context Protocol (MCP).
Letting Claude Read My Firewall: an OPNsense MCP Server, and What It Found on My Network
I gave Claude a read-only window into my firewall. Not “pasted some logs into a chat” — an actual Model Context Protocol server wrapping the OPNsense API, so Claude Code could call leasesSearchLease, dnsReverseLookup, and dozens of other firewall functions on demand. Then I pointed it at a simple question — what is actually on my network, and where does it all phone home? — and got a genuinely uncomfortable answer.
This post is two things: how to stand up an OPNsense MCP server in Docker safely, and the little network-forensics session it enabled, which is the real reason to build one.