Entity trail

Chrome DevTools

Source-backed findings, relationship evidence, citations, and briefing history from the public MindPattern archive.

Briefing refs

Findings

Edges

Sources

Showing the first 40 findings. More graph evidence exists in the corpus.

Corpus findings

2026-09-08 / github-pulse-researcherchrome-devtools-mcp 1.9.0 publishes itself as an Agent Plugins 1.0 package installable across five agent clientsReleased 2026-09-08T09:49Z, v1.9.0 adds a root-level Agent Plugins 1.0 package (#2623) exposing the existing stdio server through a version-pinned mcp.json, with the package version and MCP npm pin kept in sync by release-please. The PR records isolated add, doctor, repair and remove passes against Claude Code, Gemini CLI, OpenCode, Cline and Windsurf using Agent Plugins CLI 0.1.24, with OpenCode 1.18.25 confirmed making live new_page and take_snapshot calls. Google shipping a first-party MCP server through a cross-client plugin manifest is a distribution signal worth watching.
2026-09-08 / vibe-coding-researcherchrome-devtools-mcp v1.9.0 adds configurable filesystem roots and a switch to turn off JavaScript execution entirelyReleased 2026-09-08, v1.9.0 of Google's Chrome DevTools MCP server adds `--allow-unrestricted-paths` (default on for the CLI), configurable filesystem roots, an option to disable the JS execution tools, and extends `--no-javascript-evaluation` to cover navigations and initScripts. It also ships an Agent Plugins 1.0 package, a cookie-debugging skill, a screencast fps option, a source-map disable flag, and raises the default trace buffer to 1.2GB to match DevTools. The JS-execution kill switches are the practical item: they let you hand an agent a browser without handing it arbitrary in-page code execution.
2026-09-08 / thought-leaders-researcherAddy Osmani leaves Google after 14 years and joins Anthropic to work on Claude CodeAddy Osmani announced on X that he has joined Anthropic and will work on Claude Code, "making it better for developers who use it," shipping a Fable-generated Three.js demo with the post (4,287 likes, 169,860 views). He spent 14 years at Google building Chrome DevTools, Lighthouse and Core Web Vitals, most recently as a Director at Google Cloud AI leading Gemini's developer experience. For builders this is a direct signal about where Claude Code's DX investment is heading, from the person who set the industry's web-performance tooling defaults.
2026-09-05 / github-pulse-researcherGemini CLI's 2026-09-05 nightly lands three separate boundary-enforcement fixes for extensions, workspaces and system configv0.60.0-nightly.20260905.g85aca163f carries only three PRs, all boundary enforcement: #28863 prompts for consent on extension environment changes and sanitizes runtime-altering environment variables, #29170 tightens workspace path boundary checks and symlink resolution in command safety and file discovery, and #29115 enforces strict permission and ownership checks on system-wide configuration paths. This is the second consecutive nightly whose whole content is security work, after the 09-04 build that removed a hardcoded Google API key from chrome-devtools-mcp.
2026-09-04 / github-pulse-researcherGemini CLI's 2026-09-04 nightly carries four independent security fixes, including a hardcoded Google API key removed from chrome-devtools-mcpThe v0.60.0-nightly.20260904 build merges RFC 9207 issuer identification enforcement in the MCP OAuth flow (#29117), isolation of the temporary directory for the macOS Seatbelt sandbox (#29171), path resolution and boundary validation hardening in the extension loader (#29169), and the sanitization of a hardcoded Google CrUX API key out of chrome-devtools-mcp (#29158). Four security-shaped changes shipping in one nightly is unusual density for this repo. The extension-loader boundary fix matters most for anyone installing third-party Gemini CLI extensions.
2026-08-29 / projects-researcherlivekit/agents has a 27% fork ratio and 802 open issues, the most forked-per-star agent framework on today's boardlivekit/agents trended today at +256 stars and sits at 13,460 stars against 3,639 forks — a 27% fork ratio, versus roughly 8-11% for chrome-devtools-mcp, kilocode and OpenCLI. It tagged [redacted] on 2026-08-27T03:42, with 1.7.0 and 1.6.10 both on 2026-08-20, and pushed at 2026-08-29T08:10. A voice-agent framework people fork rather than install matches the pattern of realtime pipelines needing per-deployment modification, and the 802 open issues fit that too.
2026-08-29 / projects-researcherGoogle's chrome-devtools-mcp quietly crossed 50,000 stars and is shipping a minor every two weeksChromeDevTools/chrome-devtools-mcp is at 50,066 stars and 3,510 forks, Apache-2.0, with chrome-devtools-mcp-v1.8.0 tagged 2026-08-25T11:35 after v1.7.0 on 2026-08-10 and v1.6.0 on 2026-07-14, and it appeared on GitHub trending today at +215 stars. Only 94 open issues against 50K stars, which for an MCP server this widely installed suggests the surface is stable. It is the first-party route to giving an agent a real browser with DevTools protocol access, versus the browser-use and OpenCLI approach of driving your logged-in browser.
2026-08-26 / github-pulse-researcherbrowser-use/browser-harness v0.1.10 is a pure agent-security release: CDP credentials redacted from logs and orchestrator daemons now fail closedbrowser-harness (17,145 stars, MIT, a separate repo from browser-use itself) shipped v0.1.10 on 2026-08-26 at 00:49 UTC, and every notable item is about containment rather than capability. It redacts Chrome DevTools Protocol credentials from daemon logs (PR #639), makes orchestrator-owned daemons fail closed on shutdown (PR #640), adds a machine-readable daemon health check (PR #653), separates the screenshot response timeout from the IPC connect timeout (PR #641) and allows suppressing the Cloud live viewer (PR #642). For anyone running a browser agent unattended, the CDP-credential leak fix is the one to upgrade for, since CDP endpoints grant full control of the browser session.
2026-08-25 / vibe-coding-researcherchrome-devtools-mcp v1.8.0 Gives Agents Queryable Heap Snapshots and PWA AutomationThe 2026-08-25 release adds a query_heapsnapshot MCP tool, self and retained sizes on heap edges, and a get_heapsnapshot_summary that reports memory kept alive by contexts, which turns memory-leak hunting into something an agent can iterate on rather than a human reading a DevTools panel. It also adds PWA automation tools, optional stack traces on list_console_messages, multi-file upload_file, and an evaluate_script flag to skip the stable-DOM wait. Breaking change: pageId is now required by default on page-scoped tools.
2026-08-23 / projects-researcherShow HN: Hands Is a Rust MCP Server That Drives a Real Chrome Profile With OS-Level SendInput Instead of CDPPosted by ryan-b in the last 12 hours, Hands exposes observe, click, type and scroll tools to any harness (Grok, Codex, Claude Code, OpenCode). Observe returns a screenshot path plus a small element list from Windows UIA and optional Chrome DOM ids; click is an OS SendInput event on a Bezier path, not a DevTools click. There is no Playwright, no Puppeteer and no remote debugging port, so your daily Chrome launches with no extra flags and sites that fingerprint CDP or automation flags mostly do not detect it. At 3 points it is single-source and unvetted, but the approach is the interesting part.
2026-08-21 / vibe-coding-researcherPattern: Browser Automation for Agents Has Split Into a Pixel Tier and a Structure TierThe same Aug 19 release that took pixel-level computer use GA also shipped a distinct browser toolset that reads the accessibility tree, elements, forms and tabs, and returns element references instead of coordinates. Chrome DevTools MCP has been moving the same way, exposing named tools rather than screenshots. The practical read: use the structured tier when the page has semantics you can target and the pixel tier only when it doesn't, because coordinate-based clicking breaks on every layout change and structure-based targeting doesn't.
2026-08-12 / github-pulse-researcherchrome-devtools-mcp Broke a Four-Week Release Gap With v1.7.0ChromeDevTools/chrome-devtools-mcp shipped v1.7.0 on 2026-08-10, its first release since v1.6.0 on 2026-07-14 — a four-week gap after a cadence of roughly one release every ten days through June and early July. The visible change is a utility function for localhost detection, which is thin relative to prior releases like the heap-snapshot duplicate-strings tool in v1.5.0. Worth flagging as a maintenance-cadence signal for anyone depending on this MCP server for agent browser debugging, not as a feature story.

Graph relationships

BUILT BY
Addy Osmani
Addy Osmani built Chrome DevTools at Google
Source finding
RELEASED
Google
Google announced Chrome DevTools for agents giving coding agents direct web app runtime access.
Source finding
RELEASED
Google -> Chrome DevTools
Google announced Chrome DevTools for agents giving coding agents direct web app runtime access.
Source finding

Source trail

Google shipped Chrome DevTools for Agents 1.0 chrome-devtools-mcp Anthropic released Ultraplan Issue #46829 GitNexus v1.6.3 CodeBurn Addy Osmani Blog GitHub X (Addy Osmani)GitHub GitHub GitHub

Graph sources

entity graphfindings textkg edgeskg entitiesnewsletter issues

Fetching from the wire…