Vibe coding is fun until the AI becomes dumb all of a sudden.
by•
I used a few different tools to vibe code my saas. I used lovable, chatgpt, gemini to code my saas. The thing is, there is a huge problem of these AI's of forgetting when you chat for a longer time.
This has happened to me a lot of times. One solution I found is that you can start a new chat to overcome this problem. But, here the problem arises to explain the AI all the context which you had in the previous conversation.
Curious, has anyone else ever ran into this problem? How did you manage to overcome this?
35 views
Replies
i've had the same issue with bigger feature. now i keep a short summary of the imporatant context for the next chat.
this happen to me when a project gets more complex. i usually save the key requirments before starting a new conversation.
I have noticed the same problem when changing several parts of a SaaS at once. I now ask for a summary before ending each session and carry that summary into the next chat.
Agent 37
for me it get worse when i'm fixing and adding features together. keeping each task separate seem to help.
Bababot
i usually the AI to summarixe the project before ending a session,
A new chat only helps if the project context lives outside the chat. I keep a short repo note with the product goal, current architecture, important constraints, commands that pass, known failures, and the next three tasks. Before ending a session, I ask the model to propose an update to that note, then I review the diff rather than trusting an automatic summary. I also separate debugging from feature work: reproduce the bug, write the failing test, make the smallest fix, then start a fresh task for the feature. When the model starts contradicting files or repeating failed approaches, that is my signal to stop and create a handoff. The handoff should cite filenames and test output, not paste the whole conversation. This makes a new chat cheaper and keeps outdated assumptions from becoming permanent context.