[isolay]

> after wasting a day on this, I am now just going to go through the (single file) of code and just fix it myself.

Seriously, you wasted a whole day just so you wouldn't have to look at a single file of code?

> Update: some 20 minutes later, I have fixed the bug. Despite not knowing this particular programming language or framework.

Be really careful there, you might have accidentally learned something.

[OuterVale]

It is entirely plausible they were just experimenting with AI tooling to better understand how to use it and what it is capable of. Their saying, 'Despite not knowing this particular programming language or framework.' indicates to me this is probably the case.

[SilverSlash]

Nope. I've been working on this project for a couple of days now and things were mostly going well. A significant portion of the mvp backend and frontend was built and working. Then this one seemingly simple bug appeared and just totally stumped both Codex and Claude Code.

There was even another UI component (in the same file) which was almost the same but slightly different and that one was correct. That's what I copy pasted and tweaked when I fixed the problem. But for some reason the models were utterly incapable of making that connection.

With Codex and Claude Code I thought maybe because these agentic coding tools are trained to be conservative with tokens and aggressively use grep that they weren't looking at the full file in one go.

But with Gemini I used the web version and literally pasted that entire file + screenshots detailing what was wrong (including the other component which was rendering correctly) and it still couldn't solve it. It was bewildering.

[mlrtime]

I had the exact same issue, I had a UI scrollbar bug that claude couldn't fix, it tried 4-5 different ideas that it was sure was causing the issue, none of them worked.

Tried the same with codex, it did a little better but still 4x times around.

This is with playwright automation, screen shots, full access, etc..