Long autonomous runs to find codebase weak spots
Workflow
Run agents autonomously overnight, not mainly to get code written but to hit failure cases. A snag agents hit once every two hours shows up two or three times in a five-hour run. Fixing those spots makes shorter, supervised runs go smoothly.
Theo's current stance
Theo endorses this framing, which he credits to Jaymon: long runs expose failures faster so you can fix them.
Try it
- Give your agent a long, open-ended task overnight.
- Review where it got stuck or went wrong.
- Ask your agent to change the code so it won't hit that snag again.
First seen
12:22
way Jaymon framed this here. He likes doing overnight autonomous work not because it gets a ton of code written, but because it will hit a bunch of those fail cases so that he can architect his code base and his systems so that when he's working more in the loop doing like one or two hour threads instead of five
Every mention
12:22
way Jaymon framed this here. He likes doing overnight autonomous work not because it gets a ton of code written, but because it will hit a bunch of those fail cases so that he can architect his code base and his systems so that when he's working more in the loop doing like one or two hour threads instead of five
12:38
to 10 hour threads. If you have a speed bump in your code base that agents hit on average once every two hours, then they'll hit it on average two to three times every five hours. And if you do these super long runs, you can hit those failures faster and fix them. Learn from
Theo Daily is unofficial and not affiliated with Theo or t3.gg. Written by Claude Opus 5.5 from each video's transcript.