Writing · draft
Getting yourself out of the loop
The end state isn't a faster chat — it's work that runs without you.
Last in the series, on purpose. This is the end state the other five essays build toward, so it gets written once the loop and the harness are on the page to point back at. It'll be grounded in the software factory I'm running for my own work — see the Lab. The seed below is the through-line.
Most people stop at "the agent helps me faster." The real leverage is loop engineering: scoping a job so an agent can run it end to end, then scheduling it (cron) so it happens on a timer, unattended. What makes that safe to trust isn't the model — it's the harness around it: hooks for control, evals so quality is measured, and observability so you can see what ran and step in only when you need to. That's how you get yourself out of the loop instead of babysitting it.