One AI CLI runs my whole homelab: a single command deck, secrets in one place, and why I ripped out the no-code tool for plain Python on cron

Description and use

<p>There's one command on one box that can reach, inspect, and operate every other<br> machine in my homelab. It's an AI-driven CLI sitting at the top of the rack — think<br> of it as the estate's command deck — and underneath it is the least glamorous<br> automation stack I could build: secrets in a single vault, a pile of plain Python<br> scripts, and <code>cron</code>. No visual workflow canvas, no drag-and-drop nodes, no clever<br> event bus. I had the fancy version. I tore it out. This is why, and what the boring<br> replacement looks like.</p> <h2> The command deck: one entry point for t

Problem

<p>There's one command on one box that can reach, inspect, and operate every other<br> machine in my homelab. It's an AI-driven CLI sitting at the top of the rack — think<br> of it as the estate's command deck — and underneath it is the least glamorous<br> automation stack I could build: secrets in a single vault, a pile of plain Python<br> scripts, and <code>cron</code>. No visual workflow canvas, no drag-and-drop nodes, no clever<br> event bus. I had the fancy version. I tore it out. This is why, and what the boring<br> replacement looks like.</p> <h2> The command deck: one entry point for t

Outcome

<p>There's one command on one box that can reach, inspect, and operate every other<br> machine in my homelab. It's an AI-driven CLI sitting at the top of the rack — think<br> of it as the estate's command deck — and underneath it is the least glamorous<br> automation stack I could build: secrets in a single vault, a pile of plain Python<br> scripts, and <code>cron</code>. No visual workflow canvas, no drag-and-drop nodes, no clever<br> event bus. I had the fancy version. I tore it out. This is why, and what the boring<br> replacement looks like.</p> <h2> The command deck: one entry point for t

Evidence

One AI CLI runs my whole homelab: a single command deck, secrets in one place, and why I ripped out the no-code tool for plain Python on cron

Source