Do they have Mechanical Ventilation and Heat Recovery (MVHR) or is this more like Aircon? I've recently moved somewhere more humid and I'm looking to get a grip on what other countries do.

I mean something else. Zoom out, why do people need, or want, a tool like herdr?

What has led people to this point? Is it because they need terminal multiplexing to spawn agents, instead of using built-in subagents? Do they like cute sheep icons? What made having multiple terminals open unappealing? Is it the built-in alerting when attention is needed? Is it only applicable to people running their agents on remote machines?

When I look at these kinds of tools, that is the question I can't answer because I suspect I haven't run into the pain points they address yet, despite running multiple LLM sessions in multiple projects simultaneously.

I use cmux because I like tabbed terminals on macOS grouped by project, saves messing with our daft window management.

What is it that makes herdr et al so popular with LLM users?

Coordinating agents though? Fable any day.

It is impressive they've got the capacity to do so.

> As for GPT-5.6 Sol — it doesn't even come close. I honestly don't understand why people even try to compare them.

What kind of problems are you working on? I like Fable but when planning work on a complex C codebase it's making more mistakes than 5.6 Sol xhigh for me.

In what scenarios is Fable giving you "no errors, perfect code"?

I'm guessing this works better because it can always go back and re-analyze the saved context.

On a large C codebase, Claude hallucinates constantly, and GPT 5.5 gets there are with a lot of help, but still gets things wrong.

Could you add fff to the benchmarks?

Particularly for spoken word, it's annoying and distracting.

That sounds ideal for off-the-boil coffee brewing? At sea level I (and all the speciality coffee shops round here) aim for 91C, and I'll drop that to 88-89C for medium roast and lower if it looks on the dark side. Brew methods: Aeropress and cafetiere.

So you've now found selectors in DevTools that you think are causing the problem, and you want to find them in the source code. In the case of many projects, that means searching through hundreds of small CSS files.

That's why you grep selectors, and where the pain comes. You have to start with the most specific rules that you found in DevTools, then start deleting parts from them until you find a non-nested rule that's in the source, yet still specific enough that you haven't got hundreds of matches to go through.

It would be great if something like ast-grep could take a CSS rule copied from DevTools and search for nested CSS that would compile to match it.

It's slower to start-up than Everything but just as useful once running.

There are a few Mac oddities like OneDrive files appearing twice because macOS is convinced they exist in two locations, but that's a minor annoyance.