[vidarh]

I just had Fable run overnight in a loop, and it fixed ~150 compiler crashing bugs that Opus had kept deferring.

I wouldn't start with Fable - when I use burndown loops I tend to include instructions to document progress and set aside anything that turns out to be harder than expected, and solve the easy stuff first. When a model runs out of easy stuff and start struggling to make progress on what is left, I can let it keep churning on that - they get there eventually - or I can bump it up to a smarter model if one is available.

Opus had churned a week driving down spec failures, and did a great job. The 150 Fable took overnight were the ones Opus had kept putting aside.

[steveklabnik]

I had fable running in a loop overnight last night, finding bugs. It found a heap overflow. That triggered its safety guards, which converted the thing to opus, leaving opus to run the rest of the night, wasting my precious time with Fable.

Oh well, it was pretty funny, all things considered.

[vidarh]

That sucks - I've thankfully only had that happen once. Similar thing - I was testing my new X11 server, and it turns out that broken X11 packets can make Firefox crash, and I got a refusal on a sub-agent request Fable prompted to have an agent narrow down why.

[ianbutler]

There's a setting that stops fallback to Opus 4.8 if you would like to avoid that behavior.

Config -> Switch models when a message is flagged -> false

That should stop it entirely when a message is flagged and then you can come back without Opus having potentially made a mess.