I use a .github/copilot-instructions.md file which CodeCompanion can include automatically in the context through the memory feature. With the feature enabled the .github/copilot-instructions.md file becomes part of the conversation so that the AI can be instructed on generic guidelines to be used in the project.
The codecompanion-history plugin attempts to generate a relevant title for the conversation, but it tends to interpret the copilot-instructions.md files as relevant to determine the specific conversation as opposed to generic instructions that are not really meaningful for the conversation's title.
As example, prompting the text "Test prompt":
- Without memory it generates the title "Test Prompt Discussion".
- With copilot-instructions in memory it generate the title "GitHub Copilot Instructions for Neovim".
The first title is much more relevant than the second one.
I wonder if there is a way to generate the title more accurately by somehow excluding generic instructions from the context taken into account by the title generator.
I use a
.github/copilot-instructions.mdfile which CodeCompanion can include automatically in the context through the memory feature. With the feature enabled the.github/copilot-instructions.mdfile becomes part of the conversation so that the AI can be instructed on generic guidelines to be used in the project.The codecompanion-history plugin attempts to generate a relevant title for the conversation, but it tends to interpret the copilot-instructions.md files as relevant to determine the specific conversation as opposed to generic instructions that are not really meaningful for the conversation's title.
As example, prompting the text "Test prompt":
The first title is much more relevant than the second one.
I wonder if there is a way to generate the title more accurately by somehow excluding generic instructions from the context taken into account by the title generator.