Currently I am facing “Conversation is too long” issue in the composer. Even in new composer there is no “@codebase” option.
2 Likes
I encountered the same problem today. Reinstalling and downloading again still reports the same error.
We have a bug that was causing this to show up more frequently than it should have, but conversations do unfortunately have a fixed limit to how long they can be before the context starts to drop off from messages you send very early on.
We recommend changing to a new composer session every time you start working on a different section of your codebase, as this helps to keep the context clean and concise for the AI to work from.
With too much context can overwhelm it and stop it from understanding what it needs to down to your prompts efficiently.
Even with a new composer, It’s quite often getting stuck with “applying …”, forcing me to open up yet another composer and try again. All the time wasting credits. Is this a known bug too?
Apply’s are not done using a premium model, so should not count towards any usage.
If a code change is not applying correctly, you should be able to cancel the apply and restart it - knowing it doesn’t use any credits. Only the AI’s initial response in the chat or composer count towards your premium requests!