@sawyerhood - If you'd like to try dev-browser yourself check it out

Sawyer Hood
Sawyer Hood✓@sawyerhood
Who will win? Multi-billion dollar ai research lab or man with a markdown file? My browser skill was over 2x faster at completing this task than Claude Code's new chrome integration!
video not captured
Claude@claudeai:
Using the extension, Claude Code can test code directly in the browser to validate its work. Claude can also see client-side errors via console logs. Try it out by running /chrome in the latest version of Claude Code.
Sawyer Hood
Sawyer Hood✓@sawyerhood
The task was simple, summarize the top 5 posts on hacker news and add them to a notion doc. The built-in chrome integration took longer than the dev-browser skill and produced a much worse summary. Just look at the difference of formatting between dev-browser and the extension.
image not captured
image not captured
Read 3 more tweets
Sawyer Hood
Sawyer Hood✓@sawyerhood
Why is there a huge difference in performance? The extension takes a screenshot and decides where to click on the page each time. The skill just relies on the fact that Claude is awesome at writing code and just writes code to interact with the page.
Sawyer Hood
Sawyer Hood✓@sawyerhood
It isn't just much faster. It is much cheaper as well! In a different test I ran, dev-browser was 3x cheaper token wise than the extension.
image not captured
Sawyer Hood
Sawyer Hood✓@sawyerhood
There are some hypothetical upsides. For canvas based websites the screenshot approach will most likely perform much better, more exploration needs to be done here.

View on X →