At night, everything runs.
outerloop builds agent systems that work for hours without supervision. And the software underneath. In the morning you just sign off.
What runs at nightThe Night Shift
Agent Harnesses & Guardrails
Loops that don't derail: budgets, verification, tests, clean stop conditions. An agent running for hours isn't a risk if the frame is right.
Context Engineering
Agents aren't prompted, they're situated: memory, tools, feedback loops, knowledge in the right place. Good context replaces supervision.
Software · Apps · Web
The craft underneath: full-stack development from idea to operations. Whoever builds loops for software should be able to build software.
Enablement
Your team learns to build and run its own loops. outerloop makes itself unnecessary. That's the plan.
Signed Off
Reviews that are done by morning
Pull requests used to wait for the afternoon. Now a review loop reads every diff, tests, comments, and escalates only what a human must see. The human sees: not much.
The evening off, as a feature
A maintenance loop takes over dependencies, monitoring and the small bugs, with a budget and stop conditions. She reads the morning report instead of the alerts.
Building loops, without the tuition fee
Two weeks of pairing instead of six months of trial and error. The team now writes its own harnesses, measures its own contexts, and doesn't need outerloop anymore. Which was the point.
The Sender
good automation doesn't make you faster at the keyboard. it makes the keyboard optional.
Behind outerloop is a human: Elias Erckens-Platsch, developer and consultant from Munich. First software, then the loops around it. These days mostly context engineering and the question of how much supervision an agent really needs. Answer: less than you think, if the context is right.
How I work: small, verifiable steps. Honest reports. Systems you can switch off without anyone sweating.
Handover
step off the loop. talk to the human.
elias@outerloop.studio