Improvement of composer apply in long conversations #316
joaojhgs
started this conversation in
Ideas & Feature Requests
Replies: 1 comment 1 reply
-
|
Thanks so much for the kind words—really glad you’re finding the plugin useful! Just to give you some context, this is the prompt for apply feature. It does take in both the current file content and the full chat history. I think the issue here is that it’s including all previous messages, which can get quite long in a big conversation. That likely causes the model to prioritize older context over your more recent manual changes. I’m considering adding logic to limit this to just the last 10 to 20 messages for the apply feature. That should help reduce the kind of removals you’re seeing. Appreciate you flagging this! |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
First of all, thank you for this incredible plugin, it's been really useful, I'm excited for the features in the roadmap to come, such as external files like pdf etc.
I noticed a slight problem with the composer apply on my first long conversation, as I was interacting with the composer, I noticed that after directly changing my notes and then interacting with the composer, the apply agent always seems to default to a "last context", basically suggesting the removal of content I manually added or changed since my last interaction with it. It seems like it prioritize the value of the previous interaction resulting note over the current note context.
Of course I can just reject those removals, but as the conversation interactions start to get longer, it quickly becomes quite the bother having to reject the removal of a lot of content.
Beta Was this translation helpful? Give feedback.
All reactions