Maho vs Arc: where the agentic browser goes after Arc
Arc reached for a browser that worked the way power users actually browse. The Browser Company moved on before that idea was finished. Maho picks up the parts that mattered.
Arc reached for a browser that worked the way power users actually browse. The Browser Company moved on before that idea was finished. Maho picks up the parts that mattered.
Every browser now has a chat panel. Some of them can take action. The difference matters more than the marketing copy admits.
Browser history is one of the most useful local datasets you have, and one of the worst exposed by browsers. Here is the Maho CLI for it, with three queries worth keeping in your dotfiles.
Agentic browsers fail in four shapes. The shapes are old. The defenses are not magic. Here is what each looks like in the wild and how the Maho host responds.
Every agentic browser has three modes hiding inside it: chat, act, and refuse. The bug is when the user cannot tell which mode the assistant is in. Here is how Maho makes that visible.