I have 3 files:
- 2 files are under 230 lines and 1 around 1.2k long. All are very well commented.
- I use composer for changes and speak to the entire codebase.
- I explicitly tell it not break any existing functionality or amend anything nothing directly requested in my changes (e.g. front end design). I also ask it to ensure all functions are defined, scripts and syntax are complete and accurate. I’ll provide it with code snippets to help it (as it often fails to do itself).
- I ask one change at a time.
However, Im going around in circles. By the time Ive got one thing working, its broken something else.
I only code in python.
Is this a bug?
I’m sure others are making much more complex programs than I with far more code and complex file structure. What am I doing wrong here?
2 Likes
Maybe a long shot, but what happens if instead of chat with entire codebase you just attach all your files in composer? Is the outcome any different?
Same issue since the update!
I am having exactly the same issue.
Tried using Cursor Rules and Composer Project to tell the prompt to not remove any existing functionality, but it keeps doing so, mainly when debugging in circles whether a specific thing does not work.
I wouldn’t mind it removing it temporarily, but it should be able to add it back. I understand that it can’t “recall” what was there before, because context length, of course, but still, regarding productivity it is a lot of back and forth.
I will be trying maybe to have a @draft file where I try to instruct the prompt to write to it the current code before changing it, and whenever it gets the given feature working to merge with the @draft file and will see if it somehow helps.