A day with Fable 5 running a task and I started to hear my computer speak and play tones. I had asked it to debug an audio capture issue. In the past, Opus would either ask me to run the Smoke test wire up the devices since it required a human to test. And if this was repetitive, I would ask it to make a script or similar to do the test. But this I saw it take the initiative to do the analysis by itself. This was on a new project and I heard it say "Samantha" then a few tones, a period of silence and this continued for an hour. I spun up another claude to ask it to analyse the JSONL and understand why it was playing tones. It said: "to prove the Core Audio tap was actually capturing system audio, the test played a known audible signal and checked the captured PCM peak amplitude." This was a pipecat example with a menu bar item and nemotron-3.5-asr capturing mic and system audio. Fable wrote the menubar, coreaudio bindings, pipecat reads from these sockets and sends it to the ASR and SmartTurnModel to write full semantic sentences into a VTT-style file. One more step in loop engineering unlocked, on to the next.