The Chrome DevTools team are doing a "papercuts" sprint where they try to address lots of small, irritating bugs and annoyances.
Reply with crbug.com links (no bug, no fix—that's the deal!) and will see what we can do.
No promises though as some may be features/too big/unclear how to solve.
I'm also assuming that the legal frameworks would either need to evolve if they don't currently handle the AI codegen side of things well or put the US at a massive competitive disadvantage against somewhere like China.
Want to run one-off page speed tests without setting up monitoring?
Our new quick tests feature makes that easy, through the app or via our API.
www.debugbear.com/docs/quick-t...
We just sent out a TEST MAIL to our mailing list.
Last year quite a few people didn't see the announcement mail and missed the early bird ticket sale.
So this year we run a test first. If you're subscribed to our mailing list, please make sure you got the test mail.
Or perfnow.nl/subscribe
Has there been any movement on the legal/copyright side of AI and code (US)?
I know fully-AI-generated things can't be copyrighted. Is that still the only part settled? How about AI-assisted?
Commercial API subs indemnify but personal don't against copyright violation on generated code?
I’ve been working with a client who runs a lot of social media and ad campaigns, so we’ve been deploying the experimental `No-Vary-Search HTTP` header. It’s amazing to see it actually working! Read all about it here: csswizardry.com/2026/05/bett...
I find using different core models more useful than just picking one "best" one.
It's like getting different perspectives. They all find things the others miss and approach a problem differently.
Models from the same family or with different prompts are too similar.
I assume indemnification, even on the commercial side, still means that company has to be around and capable of absorbing your loss/risk (and that feels like a massive risk they are all carrying if something goes sideways).
Don't get me wrong, I love the tools and can't imagine working without them, I'm just concerned that the adoption may have gotten ahead of the legal frameworks.
Awesome writeup. My takeaway is really not so much that Mythos is hype as the AI security tooling in general is REALLY good so don't wait (you can bet the bad guys aren't).
Chances are that your project (open or closed) hasn't been as hardened as curl has.