Replies: 1 comment
-
Oh, I realized that by changing the custom provider name the cache gets invalidated. So I'll just put versions in the name :-). Thanks! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I wrote a custom provider for my LLM system, but I really don't want to ever have the LLM responses cached - since I'm changing it often.
I dig a bit and it seems like the cache is inside the browser's localStorage, but there is no straightforward way for me to delete only the LLM cache, since the entire cache is stored encoded in the localStorage.
The cache is very, very sticky. I tried all sorts of things and the only method I can reliably use is to slightly change the LLM input to a slightly different string, and then the LLM query won't be cached - obviously. But since the exact LLM input matters, for obvious reasons, it's not useful if you have to change it.
It would be great if there was a little UI option for wiping the cache for a given LLM, or if the LLM custom provider had an option for specifying the cache behaviour.
Is there an easier workaround I'm missing? Thanks!
Beta Was this translation helpful? Give feedback.
All reactions