This feels inverted and impractical in so many ways.

On one hand the claims are being made that AI is smart enough to replace software engineers and on other hand the website owners are beings asked to provide information in a certain format to the Agents so they can do their job better. Remember this is the same information that every regular user is able to use.

Secondly if you maintain two versions of information, one for regular humans and one for agents, its just a matter of time before they start to diverge from each other. One can pick up and compare the native app and Browser application for any company, 99% chances are they are not exactly the same.

I think it's an efficiency thing. And at scale, efficiency matters. Whether this is the right implementation idk, but when I see Claude Code use Chrome via MCP, it's incredible to see just how inefficient the status quo is.

I agree it's not a good idea, but:

> Remember this is the same information that every regular user is able to use.

This is not true. The users don't see the HTML, CSS and JavaScript. If they would, even if they're frontend devs, they'll be just as confused as the agents.

The user see images, and while you can make the agents see the image as well, unlike humans the effective agents we have today work with text, not images.

This is not a smart reply. Structure is always good otherwise why even create unit tests and compilers?

[dead]