Addy Osmani, who has long been responsible for Chrome developer experience, announced his joining of Anthropic to focus on Claude Code, aiming to improve the developer experience for coding agents.

He worked at Google for over fourteen years, contributing to front-end tools and standards such as DevTools, Lighthouse, Core Web Vitals, and TodoMVC, before moving to Google Cloud AI, where he engaged with the Agent platform, command line, and studio products. In the past year, he has publicly researched coding agent workflows and utilized Claude Code. His joining statement included demonstrations with Fable and Three.js. His profile has been updated to reflect his role as a technical staff member at Anthropic.

Claude Code is integrating browser debugging capabilities into agents: Chrome DevTools can allow models to click, run Lighthouse, and capture network and performance traces through a protocol. The tool design shifts from "humans finding issues in the panel" to "agents adjusting the same set of protocols in the terminal." Google continues to release Lighthouse categories and DevTools interfaces aimed at agents, while talent is moving towards products that turn these interfaces into everyday commands.

This transition occurs at a time when coding agents are competing for workflow entry points. Figures with research backgrounds, such as Karpathy, have also joined Anthropic this year, filling product roles that can translate complex underlying processes into muscle memory for engineers.

From a market mechanism perspective, this represents a shift of developer entry talent from browser platforms to model companies. The beneficiaries are Claude Code, which aims to turn the terminal into the default IDE; the pressured parties are the toolchains that still lock the plugin ecosystem within browser windows. Compensation and equity are valued based on model company valuations, without going through new open-source agreements.

Changing jobs does not alter the ownership of existing DevTools code. What changes is where the next generation of default debugging will occur on the screen.

Source: Public Information