One example of a "hobby grade" problem that only fable could resolve that I had no time to mess around with.
I have a home network consisting of multiple buildings, a server room with a k8 cluster and various devices, some Cctv cameras, redundant fiber links between buildings, ftth Internet and lte backup, and so on. Not a simple network. All on Mikrotik switches using a lot of modern features like L3 in hardware routing. All properly designed, servers are multi homed with 10G DAC cables between switched.
Occasionally I'd notice few second drops when observing Cctv from my cameras on the monitor attached to my pc. Pc on the 10G.
Also occasionally I'd get random devices (android TV) decide "it has no Internet) for a minute at a time.
Also occasionally I'd have my AI take 20s to answer when I know for a fact it is doing absolutely nothing.
First I looked into it myself and I found nothing. No misconfiguration etc. Then I used opus with it. It found no network drops on any interfaces etc. But it wrote a script that opened 10k connections, kept them open and sent traffic through them. This was tried to all my k8 nodes and one node would occasionally refuse to open 0.1% of these connections.
Opus decided it must be a network card or a DAC cable. It took ages to identify which. I replaced both, problem went away for weeks each time and then returned every time.
Opus had a bajillion ideas to mess with my network config. Thankfully I know enough about networking not to let it take me on a wild goose chase.
Then I used Fable. Fable took 5 minutes and found the server grade Nic card's driver I use has a known rare problem where in certain configuration the default memory buffers for some hardware offload feature are too small for it and when connections get opened rapidly it sometimes chokes.
But there are two nodes with exact same config. Why only one was affected? Actually both were affected, but on one it was so rare I had to run the testing for hours to notice it.
The memory was increased and the problem... Became a lot rarer. Not resolved completely.
Fable again. This time it came up with an idea there must be a bug in the active/standby part of the driver where it occasionally let's some traffic through the standby interface. Which makes the switches ARP learn the standby as the correct path to that mac and send a portion of that traffic there, but the standby couldn't receive traffic.
It setup tcpdump on both the standby and live and proved indeed it was happening. I do not remember how this was resolved, but it was and for last 4 weeks the problem is gone.
I have actual programming problems too. 4 of which I turned into a personal Ai benchmark. Only fable solves all 4.