It is! But it works. Native eval support will come to Workers at some point, though. We will reevaluate Kitesurf's architecture when that happens. Shouldn't be hard to migrate, we have all the logic in place now.
As we explained in the blog, tests — and WPT tests specifically — were extremely important to get Kitesurf off the ground so fast, and still are as we move to higher API coverage.
it's https://reloadium.com
tho I was wrong I do registerTool() not provideContext() because the W3C specs shows it's registerTool()
webmachinelearning.github.io/webmcp/
Last night I had a nightmare about cloudflare finally monetizing the "making sure you're not a robot" page. AI agents got the information they needed, we got ads instead ("why are you here? You're supposed to let agents do the thing. Watch some ads instead").
I dream of the day where we have the opposite. Each website you visit/scrape/your bot interacts with asks you for $0.01 as payment in lightning tokens. You pay per visit and you don't have to see ads or be tracked anymore.
Bot could look at remaining balance and decide which sites to visit. Ah, <popular resource> has raised rates to 0.025 microtokens/access, I'll have to use <secondary resource> which is still a budget-friendly 0.005 mt.
Absolutely. I have lots of fun restoring old machines; it's one of my favourite hobbies. Not only do I get a nostalgia kick from remembering systems from my younger years, but I also learn a great deal about how they worked internally and about electronics. Once they're fixed, I lose interest and move to the next project.
You can block today, Kitesurf doesn't try to hide.
https://developers.cloudflare.com/browser-run/reference/auto... https://developers.cloudflare.com/browser-run/faq/