How does the return from this browser compare with what comes out of the Claude Code harness, for example? I recently wired the Kagi MCP and I as curious the differences in what’s returned (Kagi extract vs Claude’s harness return). I didn’t realize until I did that comparison that the CC harness is already processing pages into MD and returns them into context. It also makes some choices about what to strip away before it even lands in the session. Kagi does the same, but there is less processing so the MDs come with, for example, page elements that aren’t really necessary for the query that CC’s processing strips.
How does the return from this browser compare with what comes out of the Claude Code harness, for example? I recently wired the Kagi MCP and I as curious the differences in what’s returned (Kagi extract vs Claude’s harness return). I didn’t realize until I did that comparison that the CC harness is already processing pages into MD and returns them into context. It also makes some choices about what to strip away before it even lands in the session. Kagi does the same, but there is less processing so the MDs come with, for example, page elements that aren’t really necessary for the query that CC’s processing strips.
What is the point of this?
interact with a browser with a CLI rather than MCP. I’ve found it to be faster than playwright MCP.