Video wird geladen...
Video konnte nicht geladen werden
First output looked done. Then I opened it. The bird went through the pipe like the wall was a suggestion. I stayed in the same Nex-N2.5 Pro chat and told it what the screen did. It didn’t restart the whole job. It fixed the file. Second run, collision was... show more
154,930 Aufrufe • vor 8 Tagen •via X (Twitter)
35 Kommentare

Opening the first build and watching the bird clip through the pipe is the honest review. Telling the same chat what the screen did and getting a patched file is the part that matters.

Bird clipped through wall. Told Nex-N2.5 Pro what happened. It fixed the file. No restart 🔥

Fixing a literal collision flaw through a quick chat prompt instead of manually hunting down physics matrices in the script saves an incredible amount of friction.

Most models hand over syntactically clean code that completely shatters the second it hits a runtime environment, so having an agent handle actual game loop feedback changes everything.

Pushing the agent through interactive physics debugging loops is a great benchmark challenge. Did you notice any major bounding box formatting degradation or variable calculation overlaps when it patched the file logic on the fly?

Wait which model was this? Nex-N2.5 Pro? The fact it could patch instead of restarting the whole job is huge. Most just nuke it and start over.

Staying in the same thread to feed a visual bug report straight back into the file without triggering a full reset is where agents actually start feeling like a real pair programmer.

Most models stop when the code looks pretty. This one had to survive a tap. Same chat, describe what the screen did, fix the file, second run the wall was a wall.

good job bro 🫡

appreciate brody

I find this very interesting

The fact that it fixed the file instead of starting over is nice.

That’s the real test, getting something that actually works on the screen, not just code that looks good in the output. The ability to inspect the failure and fix the same file without starting over is seriously impressive.

Syntax errors are easy convincing an AI that walls shouldn't be optional is where the real engineering starts.

Sounds like a smooth fix, glad it worked.

“代码看起来正确”和“实际跑起来正确”完全是两回事。Nex-N2.5 Pro 能根据反馈直接修文件,这个体验确实值得试试。

models stop when the code looks pretty.

They bring about testing mode

gotta give nex a try too

that’s pretty wild for a tool

without a full restart is the useful part.

“The walls are just a suggestion” — that phrase really captures it. 😂 What stands out to me is how AI can now fix specific bugs based on feedback instead of forcing you to start the whole thing over. That kind of incremental iteration is where the real engineering productivity comes in. You build, test, get feedback, fix, and keep moving. Nex-N2.5 Pro seems to understand that workflow pretty well.

Just in. Keep the reply on the product named in the post.

"The bird went through the pipe like the wall was a suggestion" 😂 This is exactly it. Most models ship pretty code. Nex-N2.5 Pro debugs it when it actually runs. No restart, just fix the file and collision works on run 2. That’s real Computer Use.

What does this do?

the ability to just patch the collision without nuking the whole file is the real win

Nice one bro

The real ones notice the quiet builders

The first run exposed the bug, but staying in the same loop and fixing the existing file is what makes the agent feel genuinely useful.

thats Code looking correct and actually running correctly are two entirely different things. Nex-N2.5 Pro can directly fix files based on feedback, and this experience is definitely worth trying out

Real-world testing separates functional AI from demos.

Solid context window 😀

The bird clipping then getting patched in chat sold me

Nex N2.5 fixes code without restarting.

Amazing to see Self-testing models, you cooked on this champ
