claude-in-chrome
A browser automation tool released by Anthropic that drives Chrome and returns screenshots or text, used in ClickOps scenarios.
Timeline (last 90 days)
Based on measurements from more than 7,500 real API counts, the median call for claude-in-chrome returning a screenshot is 1,855 tokens, while the median call returning only text is 373 tokens, with screenshot calls at about 5 times text calls.
Among claude-in-chrome calls, screenshot calls, which account for only 23%, contributed 49% of total token consumption.
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 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.
All Facts (7)
Based on measurements from more than 7,500 real API counts, the median call for claude-in-chrome returning a screenshot is 1,855 tokens, while the median call returning only text is 373 tokens, with screenshot calls at about 5 times text calls.
50%UnverifiedAmong claude-in-chrome calls, screenshot calls, which account for only 23%, contributed 49% of total token consumption.
50%UnverifiedThe 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 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%