I've created a Chrome extension called "Web2MCP" for Any Website to WebMCP: https://t.co/k6v8X0lx58
The WebMCP standard aims to allow websites to expose a set of tools for agents to use. These tools are likely to perform direct HTTP requests. Therefore, the web2mcp extension works in reverse: it automatically learns and captures the website's HTTP request list and format, generates WebMCP-standard tools, injects them into the website, and allows the agent to recognize them. This avoids interacting with the webpage by clicking UI controls; instead, it directly uses APIs to capture data and reuses browser cookies.
In a series of tests, this appears to be the fastest browser automation solution in the world. It works even better when used with the https://t.co/gDOxOTZ3v3 browser.
I've created a Chrome extension called "Web2MCP" for Any Website to WebMCP: https://t.co/k6v8X0lx58
The WebMCP standard aims to allow websites to expose a set of tools for agents to use. These tools are likely to perform direct HTTP requests. Therefore, the web2mcp extension works in reverse: it automatically learns and captures the website's HTTP request list and format, generates WebMCP-standard tools, injects them into the website, and allows the agent to recognize them. This avoids interacting with the webpage by clicking UI controls; instead, it directly uses APIs to capture data and reuses browser cookies.
In a series of tests, this appears to be the fastest browser automation solution in the world. It works even better when used with the https://t.co/gDOxOTZ3v3 browser.
Browsers were never built for agents.
Those Chrome-bridging solutions, windows flying everywhere, login states breaking at random. Not bugs. Just bridge limits.
Same task. 20% to 245% faster. Not magic.
ego lite is rebuilt from the kernel up.
Your AI agents, Claude Code, Codex, OpenClaw and more, inherit your login state directly, run in fully isolated spaces in the background, never touching your tabs.
What they get isn't a handful of CLI commands, but complete JS functions: complex multi-step operations, written once, executed once. Not "run two commands, stare at output, run two more" on repeat.
Your browser, Your agent. Together, for the first time.
You might not have noticed, but someone fixed a years-old issue with Chrome on Mac.
Window resizing, tab switching, things you do every day. The animation frame rate has long been less than half of your display's refresh rate. You felt that "not quite smooth" feeling, but probably never thought it shouldn't be that way. The video below shows it.
As of Chrome 147, it's fixed. You don't even need to be one of our users, just update Chrome to the latest version and you get it.
The person behind this is our client lead @liuwd_citro. He's landed 300+ changes in Chromium, focused on the small details that make Chrome faster and smoother, most people don't notice this work, but everyone benefits from it every day.
Why do we do this?
Cause we stand on the shoulders of countless open source projects. Building something genuinely exciting isn't possible without that foundation, so we wanna give some back.
And in a moment when AI slop is flooding the world, we still believe good products live in the details.
What's been bugging you about Chrome for a long time? Drop it in the replies. We will read every one of them. Where we can, we'll patch it.
And we'll prioritize giving you early access to what we're building.
Dear developers (and anyone who's interested in the future interface of web):
our boy @imCGQAQ just got shape() accepted as a valid value for shape-outside, which means text wraps around any curve you draw, on a left-floated figure, in one line of CSS, for every Chrome user on Earth. Chrome 149 will ship this feature next week.
shape-outside has been in the spec since 2014. for eleven years it accepted exactly five values: circle, ellipse, polygon, inset, image. want a Bézier? approximate it with 40 hand-counted vertices and live with the jagged edges. that compromise is over.
and yes — overlaps with @_chenglou's pretext. the difference: pretext is a JS text engine in userland, you build any layout on top. ours is one CSS property in the browser itself, applied to you. opposite ends of the stack.
3 demos. each is a real CSS file, no JS layout code. ↓