Chrome DevTools

@WebTwitr @tan_stack @aisdk @ctatedev @EffectTS_ @bunjavascript @GoogleAI You'll like this release github.com/ChromeDevTools… 🙂

@tan_stack @aisdk @ctatedev @EffectTS_ @bunjavascript @GoogleAI Wait until @ChromeDevTools gives us the CLI and then it'll be fullstack Chrome 🫡

I've been playing with building a personal assistant meets browsing assistant for mobile web and had to experiment with WebMCP as part of the experience. It's quite amazing to see how much better the experience can be when the browsing agent perform tasks instantly instead of wasting turns with navigating and interacting with the page to perform a task. Where as the baseline for the browsing agent I've built can navigate around and perform tasks for me, it take several turns, spends more tokens and takes more time to perform that. After implementing WebMCP into the agent harness it tasks that took several turns became instant (for pages that exposes the features). We are only at the beginning of the spec, but this is going to be amazing as more apps and sites support this feature. @ChromiumDev is building something amazing here!

@mistralvibe I would love to get working setup instructions for Mistral Vibe added to #mcp-client-configuration" target="_blank" rel="nofollow noopener">github.com/ChromeDevTools… ... want to open a PR and cc me please?

Me: Debug this INP issue. AI: I can't see your screen! Me: Enables DevTools MCP AI: Analyzed trace. Problem solved 🕵️‍♂️ Give your agent eyes → goo.gle/4qwBzKu

A feature I don't think anyone asked for. Changing scrollbar colour based on scroll-position. Use CSS scroll-based animations, custom CSS properties and Demo: colourful-scrollbar.val.run Code: val.town/x/paulkinlan/c… Probably doesn't work everywhere and probably shouldn't be used anywhere

When did they add this? Chrome devtools now shows the computed step values for css calc + variables Makes debugging 100x easier

@wesbos This was added with Chrome 138. Glad it's helpful! 🙂 Here are the release notes: #debug-css-values" target="_blank" rel="nofollow noopener">developer.chrome.com/blog/new-in-de…

We can't wait to share all the hot stuff the team is currently working on for Chrome DevTools 🌶️

Nice post by @andreban - bandarra.me/posts/point-an… - it made me think if there is a tool that is "set_preferences" that the LLM will call (with the users permission) - we could start to tailor UIs even more to the user.

Would multi-session support for the Chrome DevTools MCP server be useful for you? 🤖✖️🌍 Chime into the discussion on GitHub: github.com/ChromeDevTools…

Chrome 145 is rolling out now! ✨ It's been a Product Excellence milestone for DevTools but we’ve landed some great updates like Soft Nav markers, line-level profiler timings, and the new Render blocking column in the Network panel 📬 Read the full post: developer.chrome.com/blog/new-in-de…

Your AI agent can do more than just write code. We're exploring how the DevTools MCP server connects your model to Chrome DevTools for live debugging, from fixing high INP to testing complex forms → goo.gle/4kBqqpX

Token usage in LLM applications is a huge topic. It dictates response speed, cost efficiency - or the quota left on your plan 😄 🪫 Learn how the Chrome DevTools team squeezed a full Performance trace into Gemini in DevTools developer.chrome.com/blog/designing…

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… 🔎🗂️

#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

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

Verify your Chrome version with chrome://version. If you are still experiencing issues please let us know on social or by filing a bug through goo.gle/devtools-bug. Thank you!

We’ve identified and fixed a bug that caused considerable lag for some users of Chrome DevTools when trying to inspect elements. A fix is being rolled out with Chrome 143.0.7499.109 and later. 🐢➡️🐰 We are sorry about any interruptions to your workflows.

We've been cooking lately! 🧑‍🍳 Give it a try and let us know what you think, we are excited to keep pushing this.

Watch the full update here: youtu.be/mW6xuuFeD1A

Uh oh, glitches? 😬 Our latest What's New in #ChromeDevTools has the answers (and more!)! @jecfish @matthiasrohmer