You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Model lists now come from the provider. Claude, DeepSeek, Qwen, OpenAI, Doubao, Ollama, Gemini and Zhipu now ask their own API which models exist, rather than offering a list baked into the plugin that goes stale. A model missing from the list can still be set under "Override input parameters". (#119, #121)
Thinking appears in a callout for more models, however they send it. A provider reports reasoning either in its own field or wrapped in <think> tags, and some model families use each — Zhipu uses both. Both are handled now, and the blank lines models leave around their thinking are trimmed. (#116)
Adding an assistant opens its own settings page, where its tag and API key are.
Azure asks for a deployment name, in a text field. It was a dropdown of model names, which can never be right: an Azure deployment is named by whoever created it.
🐛 3.6.0 Fixes
ModelScope and other gateways no longer fail CORS. The bundled OpenAI SDK stamps X-Stainless-* telemetry headers onto every request, and a gateway whose allowlist does not name them rejects the request entirely. They are no longer sent. (#108)
Kimi and Grok no longer stop an answer part-way. A streamed frame that arrived split across two network reads was parsed in halves, which ended the stream mid-sentence and reported nothing. It only happened when the packets landed that way, which is why it looked random.
OpenRouter no longer reports a rejected request as a success. An HTTP error produced no text and no error, and the editor still said the text had been generated.
Image generation works on mobile. It used a Node API that mobile does not have, and threw every time.
"Override input parameters" reaches Claude, Gemini and image generation. Every key beyond a provider's own settings was being dropped there in silence.
A provider's own settings no longer leak into its request body — only declared parameters are sent.
Adding a second assistant of the same provider now names it (Qwen2), instead of saving it with no tag — which left it impossible to trigger, while still showing an entry reading # : in the command palette.
Clearing an assistant's tag now says so instead of silently keeping the previous one while the field looks empty.
Azure says which field is missing when its endpoint is blank, rather than failing obscurely.