Live data from Hacker News

Chrome DevTools MCP (2025)

developer.chrome.com

21–30 of 266 posts

Re: Chrome DevTools MCP (2025)

#21
post #4

Earlier quoted context omitted.

Of course I still watch it and have my finger on the escape key at all times :)

For now you are. All these things fall with time, of course. You will stop caring once you start feeling safe, we all do. Also. AAarrgh, my new thing to be annoyed at is AI drivel written slop. "No browser automation framework, no separate browser instance, no re-login." Oh really, nice. No separate computer either? No separate power station, no house, no star wars? No something else we didn't ask for? Just one a tog…

What can you do? I mentioned the use of AI on another thread, asking essentially the same question. The comment was flagged, presumably as off topic. Fair enough, I guess. But about 80% (maybe more) of posted blogs etc that I see on HN now have very obvious signs of AI. Comments do too. I hate it. If I want to see what Claude thinks I can ask it.

HN is becoming close to unusable, and this isn’t like the previous times where people say it’s like reddit or something. It is inundated with bot spam, it just happens the bot spam is sufficiently engaging and well-written that it is really hard to address.

Re: Chrome DevTools MCP (2025)

#22
I don’t do any serious web development and haven’t for 25 years aside from recently vibe coding internal web admin portals for back end cloud + app dev projects. But I did recently have to implement a web crawler for a customer’s site for a RAG project using Chromium + Playwrite in a Docker container deployed to Lambda.

I ran the Docker container locally for testing. Could a web developer test using Claude + Chromium in a Docker container without using their real Chrome instance?

Re: Chrome DevTools MCP (2025)

#23
post #4
post #3

Earlier quoted context omitted.

On one hand, cool demo, on the other, this is horrifying in more ways than I can begin to describe. You're literally one prompt injection away from someone having unlimited access to all of your everything.

Of course I still watch it and have my finger on the escape key at all times :)

I am in awe of the confidence you have in your reflexes.

Re: Chrome DevTools MCP (2025)

#26
Very cool. I do something like this but with Playwright. It used to be a real token hog though, and got expensive fast. So much so that I built a wrapper to dump results to disk first then let the agent query instead. https://uisnap.dev/

Will check this out to see if they’ve solved the token burn problem.

Re: Chrome DevTools MCP (2025)

#28
post #7
post #3

Earlier quoted context omitted.

On one hand, cool demo, on the other, this is horrifying in more ways than I can begin to describe. You're literally one prompt injection away from someone having unlimited access to all of your everything.

Not the person you're replying to, but: I just use a separate, dedicated Chrome profile that isn't logged into anything except what I'm working on. Then I keep the persistence, but without commingling in a way that dramatically increases the risk. edit: upon rereading, I now realize the (different) prompt injection risk you were calling out re: the handoff to yt-dlp. Separate profiles won't save you from that, though…

Even without the bash escape risk (which can be mitigated with the various ways of only allowing yt-dlp to be executed), YT Music is a paid service gated behind a Google account, with associated payment method. Even just stealing the auth cookie is pretty serious in terms of damage it could do.
Post reply on HN