Replit agent getting stuck in a loop - any advice?

[memling]

Hey, I posted two threads in the tips & tricks section for general debugging and for UI debugging you can see here:

My most useful prompt

Nice. Stick it with this one to push it to behave! Add advanced debug logging and let it guide your efforts to fix this bug. Remember to follow our chain of thought process when encountering an error. 1. propose a solution. 2. follow up with the fix. 3. But then - critically, a think about it - is this going to really work? 4. verify if it will and then proceed with your chain of thought, stop, take a breath, and then continue. We cannot have any more errors. Remember this`

Useful Prompt for UI Debugging

Another prompt which I use after I give it a command and I don’t see the correct result/feature posting to db: “list the [members, active accounts, posted to card…” and if there was an entry from a new form, and the result is error, then I will add: “I entered “whateveritis”, list and tell me if the entry was handled correctly” These are similar to yours. Make the system retrace the logic. Because that is ALL THIS IS!! a bit of goofy math logic language. ('logic language" in…

Also, I’ve found it very helpful if you can identify what the problem is yourself, or take an educated guess at it, and let the agent know what you think the problem is. For example, with UI issues sometimes the agent will get hung up trying to debug an already working implementation of a library, when the issue really is just a CSS issue. Telling the agent “I think the problem here is a CSS issue, could you check all the relevant files and try to see if the issue might be there?” works to get it stuck out of a loop of trying to implement the wrong fix.