Mainly using playwriter.dev to help debug CSS issues on the page. It's an extension you can enable in Chrome and let agents control the browser via CDP
This one works as an extension so you don't need a new browser specifically for agents. It's easier to collaborate. Also if you run the MCP in non headless mode it brings to front the browser on every interaction, like opening a new page. With the extension this does not happen.
Another benefit is context usage.
The cli can also do a lot more than other MCPs because it uses code snippets run in a stateful sandbox to control the browser, so it can do virtually anything instead of just a few exposed tools like `scroll`, `click`
I am using WebSocket hibernation so the connection will cost nothing if no events are being sent after some time, 9 seconds I think. I think cost is completely negligible. I run a similar service for the Framer MCP and it costs basically nothing even with thousands of users using it every week.
The big advantage of this architecture is that it that it's very lightweight and starts in less than 200ms. Much faster than the built in Cloudflare tunnel, and no login required
It's barely gaining adoption though. The lack of buzz is a chicken and egg issue for Mojo. I fiddled shortly with it (mainly to get it working some of my pythong scripts), and it was suprisingly easy. It'll shoot up one day for sure if Latner doesn't give up early on it.
Isn't the compiler still closed source? I and many other ML devs have no interest in a closed-source compiler. We have enough proprietary things from NVIDIA.
Yes, but Latner said multiple time it's closed until it matures (he apparently did this with llvm and swift too). So not unusal. His open source target is end of 2026. In all fairness, I have 0 doubts that he would deliver.
Use-cases like this are why Mojo isn't used in production, ever. What does Nvidia gain from switching to a proprietary frontend for a compiler backend they're already using? It's a legal headache.
Second-rate libraries like OpenCL had industry buy-in because they were open. They went through standards committees and cooperated with the rest of the industry (even Nvidia) to hear-out everyone's needs. Lattner gave up on appealing to that crowd the moment he told Khronos to pound sand. Nobody should be wondering why Apple or Nvidia won't touch Mojo with a thirty-nine and a half foot pole.
Kernels now written in Mojo were all in hand written in MLIR like in this repo. They made a full language because that's not scalable, a sane language is totally worth it. Nvidia will probably end up buying them in a few years.
CUDA Tile was exactly designed to give parity to Python in writing CUDA kernels, acknowledging the relevance of Python, while offering a path researchers don't need to mess with C++.
I really want Mojo to take off. Maybe in a few years. The lack of an stdlib holds it back more than they think, and since their focus is narrow atm it's not useful for the vast majority of work.
A browser automation Chrome extension and MCP. It consumes less context than playwright MCP and is more capable: it uses the playwright API directly, the Chrome extension is a CDP protocol proxy via WebSockets.
I use it for automating workflows in development but also filing taxes and other boring tasks
This Chrome extension allows you to control your own browser via MCP.
It bridges the CDP protocol from the MCP to the browser, meaning you can do everything Playwright can.
The MCP works using a single tool: execute. It will run Playwright code to control the browser, meaning context usage is small compared to Playwright MCP and the capabilities are more extensive
The advantage of space is that you have infinite scale. Maybe data centers in space do not work at low scale but you have to think of them at much larger scale.
Elon Musk considered data centers in space simply for the fact that more solar power is available in space than Earth
It uses opentui, the same framework uses by opencode.
It can also render diffs to images, pdf and html. Very useful for agents to share diffs in remote environments like Openclaw or Kimaki
https://github.com/remorses/critique
reply