
Product Lead for @ChromeDevTools. Ideas my own. he/him
Österreich
Joined November 2013
- Tweets1.7K
- Following273
- Followers1.1K
- Likes1.1K
Michael Hablich retweeted
🚀 API Conference #Berlin session highlights:
AI agent governance, integration, APIs as product surfaces & agent interfaces — with Frederick Elewaut, @dret, Alpesh Pawar and @MHablich.
📍 Berlin
📆 November 16–20, 2026
👉 apiconference.net/berlin/pro…
#APIConference
Michael Hablich retweeted
That’s a first: GitHub’s Advisory Database (incorrectly) flags Puppeteer as malware. github.com/github/advisory-d… We are no longer able to publish new releases.
Anyone at @github or @Microsoft who can escalate this, please?
We are entering the era of dual interface products:
- Rich UI for humans
- Token efficient API for agents
Your API is costing agents money.
I'm speaking at Agentic DevDays in Stockholm on April 28 to share how we are addressing this for @ChromeDevTools .
🤖 Made with AI
Michael Hablich retweeted
Want to give your agent quality checks?
Chrome's DevTools MCP now includes:
⚡️ Performance checks via Lighthouse
📈 Memory leak detection Skill
🦻 Accessibility debugging Skill
🎨 LCP optimization Skill
and an experimental new CLI 👀
Replying to @mistralvibe
@mistralvibe I would love to get working setup instructions for Mistral Vibe added to github.com/ChromeDevTools/ch… ... want to open a PR and cc me please?
Your #AI agent isn't picking the wrong tool because it's dumb. It's picking the wrong tool because your description didn't help it pick the right one.
Link: hablich.dev/articles/discove…
Wrote about something that's been on my mind: every browser #AI agent tool runs on CDP, which has zero auth. The security story is entirely in the layers around it. Checkout hablich.dev/articles/trust-b…
1. We spent a decade building web performance metrics around human perception.
Turns out they matter just as much when your user is an AI agent.
The reasons are completely different. 🧵
6. The mental models still hold: set a budget, measure, optimize the critical path.
But the budgets change, the measurements change, and what counts as "critical" changes when the user doesn't have eyes.
Michael Hablich retweeted
Every web developer's agent workflow: copy console error, paste into agent, wait, repeat.
Chrome DevTools MCP fixes this: ~25 tools that give your coding agent direct access to the browser.
@nearestnabors talked to @MHablich about how they built it.
youtu.be/CIOcjjgl9MI
CLI wrappers for common MCP tools is great. It only provides an optimization for half of the challenge though. What about optimizing data orchestration?
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/ch… 🔎🗂️
Michael Hablich retweeted
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/ch… 🔎🗂️
#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/ch…
#AIagents
Michael Hablich retweeted
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.













