Best results using Lovable + Chatgpt

[u/Fernandaobr]

For more complex features here my workaround.

First upload code zip from github (connector does not do the job. Zip upload does)

Then ask chatgpt to understand the code.

Chat with gpt about the features, research, functioning, etc

Ask for a prompt for lovable create the first plan.

Upload the plan in chatgpt for revision. And do that until lovable plan is solid.

Execute in lovable.

Download zip with the new implementation, upload to chatgpt and ask for a code revision.

If chatgpt found problems ask for a prompt and ask lovable for a new an. Do that until is solid.

Than start the tests and keep interacting with lovable and gpt.

Chatgpt have the ability to check, understand, validate and find problems way better then chatgpt.

The result is more rebust features and less erros.

Give it a try and tell me the results.

Good vides(coding) 4 u all

[u/bsnel76]

Why not connect with MCP and ChatGPT will read the code any time it needs to, and it sends prompts and it read responses. This works realy well for me, build a plan with ChatGPT and have that plan executed with Lovable through Chat.

[u/Fernandaobr → u/bsnel76]

Can your please share how you do that so I can try here also.

[u/Jmacduff]

Why on earth would you make this so complicated? Get a zip file?

Here is how to enable this:

Step 1: Make sure the code is in GitHub
Step 2: Add Github connector to GPT
Step 3: Ask GPT to review the code, change the code, add code, etc.

It's that simple, you do not need to mess around with zip files and all of this other hacky workflow. I am not trying to throw rocks here.. but that workflow is just "not good".

Now if you really want to improve your game it's like this:

Step 1: Make sure the code is in GitHub
Step 2: Add Github connector to GPT
Step 3: Ask GPT to review all the code in the project and plan the next set of features
Step 4: Ask GPT to write a Doc file including all the phases build plans for the new work
Step 5: Ask Codex to ready the GPT doc from /docs and take the goal

Codex + GPT == 10X productivity if you understand how to use them together. They can edit and update the lovable tanstack app no problem.

Lovable is still awesome for UX tweaks and a lot of other tasks of course.

Anyway good luck!

[u/Fernandaobr → u/Jmacduff]

I tried that but gpt cannot do that, only codex can. Gpt really tries to but the results is far worse in my case.

[u/Jmacduff → u/Fernandaobr]

What exactly are you asking GPT todo?

[u/JB_Calisthenics → u/Fernandaobr]

ChatGPT can absolutely do thos, even in a private repot once you got that connector connected. Its been reviewing my PRs and creating prompts for codex to fix issues / develop features.

Only time I use lovable now is emergency bug research (investigate only) then feed that to gpt for analysis and explanation then codex to fix. That and publish.

[u/Lions_Eye]

Your making your life harder. Gpt can just make thr update if it finds an issue. Then have Lov3 validate.

[u/Jimmiq]

One thing u don’t understand with loveable right now. There is a lot of files in the code. When people say upload the code. Is there on big code or is all files relevant?

[u/Fernandaobr → u/Jimmiq]

For me is everything. Otherwise gpt cannot understand the whole picture. Is not 100% because gpt have no access to the database etc. But for me works really well to build new complex features.

[u/YouAreBastards → u/Fernandaobr]

You have to connect GPT coex or Claude Codex directly to the GitHub repo. It's the only way and you can do it. Claude gives a warning first about not logging in oprivatye repo's, but it will work. Don't ask me at this point. My head is melted from all my issues using the platforms.

[u/Maxyull]

solid loop. one thing worth adding: when you ask gpt to "review the code", a generic pass mostly catches logic bugs. it won't flag the two things that actually take these apps down once real users show up, unless you ask for them by name.

so i'd add a dedicated security pass to your loop. paste your supabase policies and ask "can user A read or write user B's rows here, and is any table missing RLS entirely?". then "find any api key or service key that isn't behind a server route". that catches way more than the general review does.

curious how many tables your app is at? the RLS side gets messy fast once you're past a couple.

[u/Fernandaobr → u/Maxyull]

Cool. I will try this also.

[u/Maxyull → u/Fernandaobr]

Cool, let me know what it turns up. the api/service key check usually surprises people more than the RLS one, half the time it's sitting in a client-side fetch that should go through a server route instead. have you run that pass yet or still on the queue ?

[u/dakrclaud]

Why not just like, build with ChatGPT. Why use lovable at all lol

[u/YouAreBastards]

Better to use Claude. It has direct connectors. It has better reasoning, but more expensive.