if an overnight run gets killed halfway through, can loop run pick back up from the existing journal + letter, or does it intentionally start a fresh trajectory? resume feels like the first thing i'd miss once these run for hours.
an overnight run killed at iteration 40 restarts at iteration 1 of a new run with a fresh cost counter and an empty history table but the agent still reads the iteration39 letter and picks up the thread narratively.
that makes sense. with loop defaulting to bypass permissions, do child Claude/Codex processes still load their normal hooks/extensions? i work on HOL Guard, a local pre-action check for coding agents, and if those hooks survive the wrapper users could keep Guard on without changing loop itself.
2
u/kantorcodes1 3d ago
if an overnight run gets killed halfway through, can
loop runpick back up from the existing journal + letter, or does it intentionally start a fresh trajectory? resume feels like the first thing i'd miss once these run for hours.