I think this is noteworthy in that it is using what is increasingly becoming the dominant API protocol for LLM.

Just because the wheel exists doesn't mean we shouldn't strive to make it better by applying new knowledge and technologies to it.

Competitors don’t just challenge you, they push you to deliver your best work.

none of these have stuck right. And none of them work well enough that all web dev agencies no longer have to worry about e2e testing. (or do some of them? Maybe the market is simply that inefficient).

I don't see this being a solution for full e2e regression testing. Having to run inference for each command/test seems expensive. I do think there's room for self-healing tests after failure.

If this works well enough couldn't you save the selectors and only use inference running the test for the first time and when the UI has changed. Cheaper than dev?

that would be a good feature. though there are already playback and record tools to do just that. I really only see this for low-code users who want to automate a novel task.

This is a bit disingenuous, no? None of these have actually taken off.