I’ve been thinking about how AI desktop clients like ChatGPT and Claude are expanding beyond chat. With MCP, MCP Apps, and now WebMCP, they could start interacting more directly with services and websites.
I gathered a few thoughts about what that might mean for browsers and wrote a short post about it.
Looks Cool! Navigation is good overall. But It would be great if I could use ArrowUp/ArrowDown to scroll in scrollable areas and focus on buttons as well.
A few hours ago. I am learning a new language (rust) so I disabled auto complete and AI suggestions. Otherwise AI becomes more of a distraction than a booster.
But for languages I am more confident (like JS and dart), I usually don't write code and only review it.
If it is a throw-away project (like I am only experimenting something or just need something for one time), I don't event look at the code and only focus on the outcomes.
As the article states, it is a "wild experiment". I wouldn't let AI control anything serious end to end. Also if Claude really becomes JIT, it is going to be an expensive one.
I was building AI agents that browse the web and kept hitting the same wall: sending screenshots or accessibility snapshots to the model burns tokens and is slow. So I tried rendering pages as ASCII wireframes instead.
Every interactive element gets a numbered label. The agent sees a compact text representation and says "click [12]" or "type [5] hello". A typical page costs 3x to 10x less tokens depending on the content.
You can use it with the Vercel AI SDK or as an MCP server. To add it to Cursor or Claude Desktop:
I gathered a few thoughts about what that might mean for browsers and wrote a short post about it.