[arthurgousset]

Cursor often gets into "dead loops" trying to fix code [1][2]. But, Cursor also seems to get out of dead loops when it adds `console.log` statements everywhere.

We thought: "What if Cursor could access Node.js at runtime?". That would save it from adding `console.log` everywhere, and still get out of dead loops.

We looked into it and got Cursor to debug Node.js on its own.

It's a prototype, but if you're interested in trying it out, we'd love some feedback!

Github: github.com/hyperdrive-eng/mcp-nodejs-debugger

---

References:

[1]: "At this point I feel like giving up on Cursor and just accept that WE'RE NOT THERE YET." ~Source: https://forum.cursor.com/t/cursor-for-complex-projects/38911

[2]: "We've all had the issue. You're trying to build a complex project with your AI companion. It runs into a dead loop, coding in circles, making suggestions it already tried that didn't work." ~Source: https://www.reddit.com/r/ChatGPTCoding/comments/1gz8fxb/solu...

[bulatb]

> Cursor often gets into "dead loops" trying to fix code [1][2]. But, Cursor also seems to get out of dead loops when it adds `console.log` statements everywhere.

Hah. That sounds like just... debugging.

[arthurgousset]

Yes! Cursor really wants to debug. Personally, I don't love when Cursor adds 100s of `console.log` diffs to my project. I like debuggers for that.

[kilroy123]

That's what console ninja's new thing is supposed to do. I haven't used it yet as you have to pay.

[arthurgousset]

Not affiliated with Cursor, but I think there is a free plan to try Cursor out. It's still a bit janky in my opinion, but it's an interesting new dev experience.

[dsabanin]

I haven't seen console ninja yet, thanks for mentioning it. It’s amazing!