Gianni Leggio

Your mission, should you choose to accept it: the agents are running in the lab, three rooms and one network hop away, and you are standing in a queue with a phone in your hand. The work cannot wait for you to sit back down. The approval blocking it is one tap away. The agent will hold the line until somebody answers, and the somebody is you. I already moved my coding agents off the laptop, in Ghost Protocol . They run on an always-on box in the lab now, unattended, writing code at 3am while the laptop lid is shut. That solved the compute problem and left a smaller, dumber one in its place: the console was still in the lab. ...

Your mission, should you choose to accept it: the agents working your codebase don’t stop when you close the laptop lid. They can’t. Hand the operation to a machine that never sleeps, never closes, and never goes dark mid-run. This message will not self-destruct. Neither will the pipeline running at 3am without you. The Job Changed Underneath the Laptop For years the case for getting off the laptop was personal inconvenience: the battery hits 3% mid-refactor, it’s asleep in the other room when the fix finally clicks, one spilled coffee away from a very bad afternoon. Real problems, but survivable ones. Commit often, back it up, hope for the best. ...

Two failures. One evening. Both lied. First, a validation error with values that were clearly fine. Then, a send-to-printer command that disappeared into silence. No confirmation. No error. Nothing. The mission: determine what actually broke. Not what the dialog box claimed broke. Not what the forum said probably broke. What actually broke, isolated layer by layer, with evidence. I print miniatures. I run a Bambu A1 with a 0.2mm nozzle and community profiles for tabletop minis. Orca Slicer is my tool of choice because it gives me more control than Bambu Studio. That control comes with a cost: when things fail, you’re on your own. ...

The electrician was standing in front of my panel. Rows of switches. None labeled. He had a marker. He put it back in his pocket. I asked why. “Because I’m not sure which does what. And a wrong label is more dangerous than no label.” The next electrician would trust it blindly. He walked away. The switches stayed blank. I thought about that for a long time. Then I recognized the pattern everywhere in software. ...

Good morning, Agent. You’ve been running Docker inside LXC containers on Proxmox for over a year now. Seven containers. Seven little fortresses, each housing its own Docker Compose stack. Immich, Frigate, Jellyfin, the Arr empire. Clean separation. Independent backups. Feels right. Then someone drops a Reddit thread in your lap: “Docker in LXC is an antipattern.” Time to audit the operation. The Setup Under Scrutiny Here’s how the Minilab is architected. Every service gets its own LXC container on Proxmox, and inside each one, Docker runs the actual application: ...