-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEAT]: Remove the [CONTEXT 0][CONTEXT 2][CONTEXT 5] information #2658
Comments
You can usually work around this with a tweaked System Prompt:
Another good method is to create a "new" model, with some existing conversation already baked into the model file:
|
How are you using AnythingLLM? The context is in the system prompt so that shouldn't be showing in an LLM response, and if it does that is just a model behavior. I haven't had it return context snippets in the response before |
Hi together and thanks for the answers, i have read a little bit and it looks like perplexity is delivering these [context x] "informations" inside the streamed text response. Here are the tokens that are coming from perplexity: [backend] info: Original Token: -Wissen So i think there isnt a good way to filter them out. |
Ah, seems like a model behavior. I wonder if swapping that to XML would help. Lots of training data is XML/HTML so it may be better are stripping that out of the response. What perplexity model are you using so i can try to repro? |
any news about this? is it fixable or do we have to live with it because its a problem only on perplexity-side? |
What would you like to see?
Hi together,
i am playing around with anythingllm connected to perplexity and its working good, but all responses are containing [CONTEXT 0][CONTEXT 2][CONTEXT 5] inside the text which makes it hard to read.
I have tried to filter it out by prompt but it seems to be impossible.
Would great if anyone has an idea how to filter it out in the response as it doesnt help anyone as nobody knows whats [CONTEXT 5]
The text was updated successfully, but these errors were encountered: