After working with Copilot for a while now, my biggest issue with the system is it’s forget fullness, which will cause it to re-generate entire existing modules (in a new location of course, with all new names) simply because it ‘forgot’ that entire module already existed…

Yes, Codepilot will vomit new code all over your code base real quick if you let it. My experience is 5 minutes of insanely productive code generation (as in, it generates in 5 minutes what takes a normal human being days, or even weeks, to code manually), followed by hours and hours of painful cleanup sessions…
This is all made worse by my second biggest gripe with Copilot. He seems to be quitte a coward.
You see to me, duplicated code is simply wrong and the right thing to do is to REMOVE the duplication. But CoPilot is a bit of a b*tch when it comes to removing any of the tons of code it vomitted all over your codebase in just 5 minutes… Either you revert everything or you attempt clean-up, but Copilots idea of cleanup is, lets not actually remove the code, lets re-export it. Lets create a NEW file, that has an alias to the code I asked it to remove… It can become quitte a game of whack-a-mole!!
And then I discovered that it is not the AI’s fault. At one point it told me cleanup was complete but I still see the original (duplicate) file sitting there so I give him the output of an ls command and ask it what is up… He tries again… Just read this:
So is our conclusion you are simply not capable of removing files??
stijn@stijns-mbp moebius-vm % ls -a src/proto
. core-types.ts
.. reversible-accumulator.tsTwo attempts to simply run
rm src/proto/core-types.ls, both failed, Twice you act like it succeeded?Can you not simply verify whether deletion actually worked with
ls -a src/proto????
Considering file deletion
I’ll remove core-types.ts and then re-check the proto listing to verify removal.
I attempted to delete core-types.ts but the edit tool returned no change and the file still appears in the repository listing:
Current proto contents (from workspace search)
What happened
I called the repository edit tool to delete the file, but the patch had no effect (the tool returned empty). That means the patch wasn’t applied here — I can’t tell exactly why from the tool response, only that the file remains.
