Yesterday Anthropic shipped a sandboxed browser inside the Claude Code desktop app. Cmd+Shift+B, and your agent can read docs, click through a signup flow, and poke at your local dev server without ever leaving the session. The announcement is sitting at roughly 1.7 million views and 16,000 likes in a day, which for a developer-tool feature is a small earthquake.
Here is the part nobody at the launch party mentioned: developers already voted for this feature, months ago, with installs.
What were developers installing before the browser arrived?
The install counts below come from the Skillselion live catalog, refreshed daily from skills.sh, GitHub and MCP registries, ranked by real installs.
- agent-browser (GitHub) - Vercel's browser-automation CLI for agents. 533,255 installs, which puts it in the top handful of skills across the entire catalog. Not top of the browser niche. Top of everything.
- playwright-cli (GitHub) - Microsoft's Playwright driver for agent sessions, 82,449 installs.
- playwright-best-practices (GitHub) - 59,422 installs for a skill that just teaches the agent to write non-flaky tests.
- chrome-devtools (GitHub) - 13,334 installs from GitHub's own skill collection.
- chrome-devtools-mcp (GitHub) - the Chrome team's official MCP server, 4,923 installs against a 46,640-star repo.
- browser-automation (GitHub) - 5,732 installs.
- a11y-debugging (GitHub) - 1,439 installs for accessibility audits driven from the agent.
Add that up and you get well over 700,000 installs of "give my coding agent a browser" across one directory. That is the single largest capability gap developers have been patching by hand.
Takeaway 1: browser access is the gap between an agent that writes code and an agent that verifies code. An agent that cannot load the page it just changed is doing open-loop control, and every developer who installed one of the tools above had already figured that out.
Does the built-in browser kill the browser-skill stack?
Mostly no, and the reason is scope.
The in-app browser is sandboxed and session-scoped. It is excellent at the read-and-poke loop: pull the docs for the library you are wiring in, click the button you just rendered, check the network tab equivalent, iterate. The tab-switching tax on that loop was real, and it is gone. That is what 16,000 people were cheering.
What it does not replace:
- CI-grade end-to-end testing. Playwright skills exist so the agent writes tests that survive after the session ends. A sandboxed session browser produces no artifact your pipeline can rerun. The 82,449 installs of playwright-cli are not going anywhere.
- Performance work. Tracing layout shifts and LCP regressions is DevTools-protocol territory, which is exactly why the Chrome team ships chrome-devtools-mcp as a full MCP server rather than a browsing feature.
- Accessibility audits. a11y-debugging runs structured checks, not clicks.
- Anything headless at scale. Crawls, form-fill batches, screenshot matrices: agent-browser exists precisely because a visible single tab is the wrong tool for that shape of work.
Takeaway 2: the built-in browser replaces glue, not the stack. Verification is consolidating into the agent, and the specialized layers (test generation, DevTools traces, a11y) are the parts that compound.
What should you actually do on Monday?
If you are on the Claude Code desktop app, update and try Cmd+Shift+B on your own dev server. Then look at what the heavy installers pair with it: the best-of catalog ranks browser, testing and debugging skills by live install counts, so you can see which of the tools above developers keep after the honeymoon.
The agents got eyes this week. The interesting question is what they look at.
I help maintain Skillselion, a directory of Claude Code, Codex and Cursor extensions ranked by real installs. Stats above are live catalog numbers as of July 11, 2026.
Top comments (0)