AI assistance in Chrome DevTools is here with Chrome 131! 🚀 Using Gemini, it helps you debug styling issues, understand layouts, and get AI-generated fixes for CSS bugs. Learn more → goo.gle/3B6N6fk

Here is Gemini CLI’s September 15th weekly update for v0.6.0 - 🎉 Higher limits for Google AI Pro and Ultra subscribers: we’re psyched to finally announce that Google AI Pro and AI Ultra subscribers now get access to significantly higher 2.5 quota limits for Gemini CLI! -

We just released the Chrome DevTools MCP server. Checkout developer.chrome.com/blog/chrome-de… for more details. For years, we’ve built DevTools with human developers in mind. Now we’re also starting to build for AI systems as first-class users.

Great to see devs already tinkering with the Chrome DevTools MCP server 🚀 Lots of useful feedback via issues and PRs, and we shipped improvements within hours. Keep the feedback coming on GitHub 👉 github.com/ChromeDevTools…

The Chrome DevTools MCP server is now also published on the GitHub MCP registry: github.com/mcp/chromedevt…

The Chrome DevTools MCP lets my AI agent speed up my website for me. This is the future. Incredible work Michael Hablich and Mathias Bynens

We just released version 0.5.1 for the Chrome DevTools #MCP server , and it's a big one for compatibility: we've added *Node.js 20 support*! We saw that many of you were running into issues with older Node.js versions. github.com/ChromeDevTools…

Building the Chrome DevTools MCP server means learning from how others use it. Developers asked for more flexibility, so you can now pass any Chrome command line argument through to the actuated Chrome instance. GitHub: github.com/ChromeDevTools…

The Chrome DevTools MCP server is now also available as Claude Code plugin github.com/ChromeDevTools….

Building for AI agents feels new, but the craft is familiar. We still do discovery, form personas, and build empathy, just through different signals. #ProductDiscovery #AI #ProductManagement

Hot take: I think MCP clients should provide better error messages when an MCP server is failing. It's so frustrating to debug MCP setup errors.

A lot of coding still happens with a human at the steering wheel and an AI agent as copilot. With the Chrome DevTools MCP server, you can start debugging in DevTools and let your AI agent pick up where you left off.

MCP is a very generic interface for agents to call functions. It’s a tradeoff between interoperability and efficiency: great if you want any MCP-capable agent to use your API, but you pay abstraction overhead vs direct calls. Feels like a 2025 WSDL. #MCP #AIagents #APIs

We are contemplating supporting #MCP Apps in the Chrome DevTools MCP server. If you have an opinion, please add a comment to github.com/ChromeDevTools…

Glühwein and web tech, what more can you wish for? ;-)

People might appreciate this, at least plenty of people requested this feature: developer.chrome.com/blog/chrome-de…

Let your coding agent debug your active browser session directly → goo.gle/4iSz0PV This new Chrome DevTools MCP enhancement lets you seamlessly switch between manual and AI-assisted debugging for faster fixes.

#MCP is great for agent-to-tool communication. But 50 sequential browser operations = 50 round trips = latency and token overhead. I opened an RFC for a CLI wrapper that lets agents batch operations via bash scripts. github.com/ChromeDevTools… #AIagents

The team is thinking about extending the Chrome DevTools MCP server with GraphQL support. Let us know what you think on the RFC: github.com/ChromeDevTools… 🔎🗂️

CLI wrappers for common MCP tools is great. It only provides an optimization for half of the challenge though. What about optimizing data orchestration?