The errors are infrequent enough that this normally wouldn't be an issue for me.

Except, starting this morning, one very long running session decided to start spawning subagents for each task. I'm not sure what caused this emergent behavior, but it seemed to be working fine, so I was eager to see where it went.

Except, as soon as a subagent hits a 500 error, the main agent seemingly doesn't know what to do. It kind of panics—"now the tree/install state is unknown!"—and ultimately does a git checkout "to verify and restore a known-good state before anything else".

I've paused the job for now since it's a sort of background experiment.