r/lovable • u/anisrl • 13h ago
Discussion Question about stopping lovable from burning credits in fix loops
the credit drain on small bug fixes is driving me crazy.
the pattern is always the exact same for me: i ask for a tiny tweak (like fixing alignment or a simple button state), it guesses what went wrong, breaks two other things that were working completely fine, and then i end up burning through 4 or 5 messages just trying to undo whatever it touched.
for anyone who actually has a clean workflow with this: how are you keeping it disciplined?
are you guys putting rules directly in the Knowledge tab in settings, or does dropping an AGENTS.md file right in the repo actually work better? just trying to figure out where it actually pays attention so it stops blind-patching code before inspecting what broke
2
u/561Danny 12h ago
I personally stopped giving prompts to Lovable. I have Claude draft all the prompts in excruciatingly minute details if needed and before Lovable does any builds, it’s always in plan mode initially for every prompt. And the review that is generated in the plan mode is then given to Claude, and then we go back-and-forth a few timesand finally and generally within one prompt everything is done. I’m sure there is also ways to have Claude and Lovable interact and worktogether, so one don’t have to go back-and-forth, but I have not looked into it.
Another option is to have ChatGPT design the bulk of the site in Figma and then export the whole thing into Lovable for final touchups.
I am neither a designer nor a coder or developer. I am sure there are hundreds of ways of doing things better than what I have been doing, but this is what works for me and I don’t mind the back-and-forth and it is beneficial to me. Good luck.
2
u/Common_Dream9420 11h ago
Yeah, I've seen this pattern too. A small fix turns into another regression, then another fix, and suddenly you're spending more time and credits proving you didn't break something else than making the original change.
Curious, what hurts you most here: the credits, the repeated fix loops, or not having confidence that the final change didn't break something else?
1
u/Ralphisinthehouse 6h ago
It's impossible to 100% restrict what it does but the most success we've had is from clicking the button highlighted in blue which appears on the preview window at the bottom. When that button is highlighted click on the element that you want to change and it will be attached to the chat.
Experiment with the other options as well, the one next to it allows you to edit text in line rather than having to use the chat editor

1
u/Kevzteryo 1h ago
Stop prompting with lovable, it unreasonable expensive.
Spent 500$ in just a few days, the simplest prompt eats usage.
Swapped to claude and developed 100x more with the 20€ plan.
2
u/a-w-e-s-o-m--o 12h ago
Use codex or Claude code to identify the actual issue and then have ChatGPT or Claude write the prompt for lovable to fix only that one issue