opencli
A command-line tool that extracts web page content as plain text through an already logged-in Chrome browser, used to reduce token consumption in browser automation.
Timeline (last 90 days)
The median tokens per call for opencli is 397, roughly on par with claude-in-chrome's text-only calls (373), with the entire gap between the two coming from screenshots.
In a comparison across 9 websites, opencli consumed fewer tokens than claude-in-chrome on 7 websites, and after weighting by number of calls, reduced token consumption by about 27% per call on average.
On telegram.org, the median tokens per call for claude-in-chrome is 1,879 and for opencli is 275, an 85% reduction, making it the website with the largest gap.
On the Bing website, opencli instead used 31% more tokens than claude-in-chrome (353 vs 270), but this row has a sample size of fewer than 30 calls, so the conclusion is for reference only.
The recommended tool priority decision rule in the clickops scenario is: when an API or curl is available, use the API first; next, use opencli to read the page as text; only take a screenshot when visual elements need to be inspected.
The limitations of this measurement method include: the website comparison matches calls by the same website rather than A/B testing the same task; screenshot results remain in the context and are re-read by subsequent rounds but their cost is excluded; and some websites have small sample sizes.
Tools such as opencli drastically prune the DOM, first converting the page into an accessibility tree or semantic Markdown, discarding styles and decorative nodes, and retaining only semantic elements, thereby keeping a single call under 400 tokens.
All Facts (7)
The median tokens per call for opencli is 397, roughly on par with claude-in-chrome's text-only calls (373), with the entire gap between the two coming from screenshots.
50%UnverifiedIn a comparison across 9 websites, opencli consumed fewer tokens than claude-in-chrome on 7 websites, and after weighting by number of calls, reduced token consumption by about 27% per call on average.
50%UnverifiedOn telegram.org, the median tokens per call for claude-in-chrome is 1,879 and for opencli is 275, an 85% reduction, making it the website with the largest gap.
50%UnverifiedOn the Bing website, opencli instead used 31% more tokens than claude-in-chrome (353 vs 270), but this row has a sample size of fewer than 30 calls, so the conclusion is for reference only.
50%UnverifiedThe recommended tool priority decision rule in the clickops scenario is: when an API or curl is available, use the API first; next, use opencli to read the page as text; only take a screenshot when visual elements need to be inspected.
50%UnverifiedThe limitations of this measurement method include: the website comparison matches calls by the same website rather than A/B testing the same task; screenshot results remain in the context and are re-read by subsequent rounds but their cost is excluded; and some websites have small sample sizes.
50%UnverifiedTools such as opencli drastically prune the DOM, first converting the page into an accessibility tree or semantic Markdown, discarding styles and decorative nodes, and retaining only semantic elements, thereby keeping a single call under 400 tokens.
50%