Comment by _pdp_
2 days ago
Doom loops are as much of a model problem as it is deficiency of the harness. I have not seen any other open source harness that deals with them except the one I started because of this obvious gap.
See my other comment with examples where 0x Alpha is working non-stop on various projects with zero problems.
Pi.dev has an extension that does it. None of the models I use seem to have that failure mode so I haven't bothered throwing it in.
The failure mode I run into commonly is agents just stop sometimes. Even sending a "." Or something they start back up, but I haven't worked out exactly how to fix that generally in harness, bit unclear how to tell if they're done or just derped to a stop.
How do you recover from doom loops? Just send the same prompt again and pray that it works, or anything more sophisticated?
I'm not 100% sure what I'd do to detect this for shells specifically, maybe prompt the user, but my toy harness scolds refuses to re-read files because the previous iteration of GLM was room-looping on that. Clearly something that they need to work on.
detect, slice & dice, re-prompt
It feels like all these models are missing a long horizon orchestrator of some kind. Humans don't think in a single thread, they have thoughts that appear, pause and disappear.
The reason humans don't go into a doom loop is because of this ability of other thoughts to interject and say, no this is stupid.
1 reply →