From a07f18617f2fcef2d743552bee58c3aee261a68e Mon Sep 17 00:00:00 2001 From: nesquena-hermes Date: Thu, 24 Sep 2026 16:53:40 +0000 Subject: [PATCH] docs(changelog): #7632 keep per-profile models cache across profile switch --- CHANGELOG.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 1586e436..af3bee87 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -44,6 +44,11 @@ ### Fixed +- **Switching profiles no longer rebuilds the model list from scratch.** A profile switch used to + delete the saved models cache, so the next model-list load re-queried every provider. Each + profile now keeps its own cached model list across switches. The cache is still thrown away when + that profile's `config.yaml`, `.env` values, or model-provider plugins change, and when the + profile is deleted or recreated. (#7632 by @carlotestor) - **Picking a model from a named custom provider sends the right model name.** Choosing a model that belongs to a non-default custom provider (for example `@custom:my-server:model-x`) sent the whole picker id, prefix included, to the provider, which rejected the request. The