Thank you. No config atm to declare which fields are "stable" for caching. I assume you mean cases where the user would provide a different session ID but still would prefer the key to match. Am I right?

Hey, contributor here. That's right, GoModel embeds requests and does vector similarity lookup before proxying. Regarding the cache invalidation, there is no "purging" involved – the model is part of the namespace (params_hash includes the LLM model, path, guardrails hash, etc). TTL takes care of the cleanup later.