This is the one post in the series you do, not just read. By the end you'll have a single Telegram topic where you type a message and a coding agent answers and drives a tmux pane on your own box. That's the entire goal, nothing more. Memory, monitors, tool servers, and the supervisor all come later; none of them are needed to get an agent answering you.
Budget ~30–45 minutes. If you only do one thing, do the Fast path, then prove it with the readiness gate. Everything below the gate is manual explanation and debugging you can skip until you need it.
Prerequisites (where solo setups die)
The Telegram wiring is the mechanical part; the real failures hide in local state. Confirm every line before you start:
A box you control with tmux, and shell access that survives disconnects (you'll leave a gateway running).
