Open michaelneale opened 1 week ago
I think this may be able to be addressed with a moderator: a moderator which drops old content smartly especially if it knows there is a new version of the file.
Agree! pruning reads from the history based on path probably improves performance and should also drop context naturally quite a bit
Even though it knows file has changed, it is unable to "forget" the old content of the file from its context.
Result: often old unwanted changes make their way back into a file, if you have edited it outside of the goose session.
Solution: probably need to prune past content of the file in the current session once it is detected to have changed, if at all possible.