News for hackers. Stuff that matters.

A comment on If AI writes code, should the session be part of the commit?. Parent comment

Re:If AI writes code, should the session be part of the commit? by jumploops on Monday March 02, 2026 @03:41AM (#47215349)
This is great, giving agents access to logs (dev or prod) tightens the debug flow substantially.

With that said, I often find myself leaning on the debug flow for non-errors e.g. UI/UX regressions that the models are still bad at visualizing.

As an example, I added a "SlopGoo" component to a side project, which uses an animated SVG to produce a "goo" like effect. Ended up going through 8 debug docs[0] until I was satisified.

[0]https://github.com/jumploops/slop.haus/tree/main/debug

[ Parent | on HN ]
Re:If AI writes code, should the session be part of the commit? by nubinetwork on Monday March 02, 2026 @05:43AM (#47216209)
> giving agents access to logs (dev or prod) tightens the debug flow substantially.

Unless the agent doesn't know what it's doing... I've caught Gemini stuck in an edit-debug loop making the same 3-4 mistakes over and over again for like an hour, only to take the code over to Claude and get the correct result in 2-3 cycles (like 5-10 minutes)... I can't really blame Gemini for that too much though, what I have it working on isn't documented very well, which is why I wanted the help in the first place...

[ Parent | on HN ]