self-published benchmark in README claims a 16% lower workflow token cost than Vercel's agent-browser on a Google Flights task (plus a much smaller install footprint).
I was using https://www.brow.sh/ for page fetching. This looks more interesting, but also it is just wrapper around Chrome Developer Tools? `kuri-fetch` is not stand-alone then, it needs chrome running somewhere.
self-published benchmark in README claims a 16% lower workflow token cost than Vercel's agent-browser on a Google Flights task (plus a much smaller install footprint).
I was using https://www.brow.sh/ for page fetching. This looks more interesting, but also it is just wrapper around Chrome Developer Tools? `kuri-fetch` is not stand-alone then, it needs chrome running somewhere.
In the comparison table, kuri-fetch is described as "no Chrome needed".