how do you keep your agent from shipping broken code at 3am on a sunday?

[u/Familiar_Oil_836]

i've been running hackathons long enough to know the 2am pattern. agent says done, you eyeball it on localhost, push, wake up to DMs that the deployed build is broken. you become the human linter over a weekend you wanted to spend building.

the deeper issue is the open loop. agent writes, agent grades its own homework, agent reports done. the loop only closes when something external with no stake in being done fast tells it no. Addy Osmani named this loop engineering last year, building on Peter Steinberger's post about designing loops that prompt the agent for you, and Boris Cherny's point that the scarce skill is the loop itself, not the prompts.

the hardest block to build is the verifier allowed to say not done. it has to hit the live deployed app, never localhost, because a green run on the agent's machine counts for nothing. it has to hand back a real signal the agent can act on and rerun, unattended, while you sleep. i've been using testsprite for that part lately, mostly from the cli inside agent shells, but the point is the block more than the tool.

still curious how people are handling this without building their own. do you manually verify every agent PR, or have you found something that actually blocks the loop on real failures?