A short, real walkthrough. Headless Maho on macOS, a single fetch, a structured extract using named extractors, then a batch run over a URL list. Where this overlaps with Playwright and where it does not.
Most browsers treat the keyboard as accessibility, not as the primary interface. Maho’s bet is the other direction. Here is the model, the cheatsheet, and the places we still owe you better.
The instinct is that local is free and cloud is expensive. The numbers are more interesting than that, and the crossover happens later than most people think.
We described the shape of Maho sync in an earlier post. This is the long version. Real primitives, real wire format, real threat model.
Firefox built the user-agency case for the page-rendering era. Maho is building it for an era where the browser also runs models and tools. Both arguments are still right.
