before version 40.0, I can pin the most-use context.
But now, the feature is gone. 
that I can’t find it.
2 Likes
Hey, we removed this feature as it wasn’t really working as intended.
When you write a prompt, and @ a file as context, the LLM is given the most relevant sections of the file relating to your request. However, when you pinned a file, the same process would happen over and over, causing the prompt to be full of repeated code and nothing new for the AI to see.
For context, when you send a prompt and @ a file, any subsequent messages will also share the same context, but be limited to the most relevant sections. If you are jumping to a different section of a large file, I’d recommend @ing the file again, to ensure the most relevant sections are provided to the AI.
I understand what you mean.
Thank you for your reply.
I can put the commonly used context in a notepad. That way, the problem can be solved too.
ha ha ha ha~~ 
.
1 Like
That’s fairly bad UX. So, if I understand correctly, it’s now impossible to have default files for chat or composer (which would only need to be inserted for the first message by system to AI), and users must manually add them every time? 
Hey, while pinning context is gone, this was removed as the same context was being provided in every message, which didn’t serve a purpose as it would also be available from the older messages.
We have some changes in the works around context which may improve your experience soon!
2 Likes
Looking forward for this! Very useful when you have some helpers function in a separated file that you want to be considered at all the times.