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
docs(readme): clarify that explicit provider config does not require listing models
Split the previous combined example into a minimal URL/auth override and a
separate optional curation example, so users no longer think they must declare
each model under `models` to make the plugin work.
Copy file name to clipboardExpand all lines: README.md
+22-3Lines changed: 22 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -89,9 +89,9 @@ If LiteLLM is on `localhost:4000`, `:8000`, or `:8080`, the plugin self-configur
89
89
}
90
90
```
91
91
92
-
### Explicit provider
92
+
### Explicit provider (custom URL or auth)
93
93
94
-
Override the URL, set an API key, or pre-define curated models that the plugin will preserve:
94
+
You **do not need to list any models** — the plugin still discovers them from `/v1/models` automatically. Use this form only when you need to point at a non-default URL or pass an API key:
95
95
96
96
```jsonc
97
97
{
@@ -101,6 +101,25 @@ Override the URL, set an API key, or pre-define curated models that the plugin w
That's the whole config — every model in your LiteLLM `model_list` will appear in the picker.
114
+
115
+
### Overriding or curating individual models (optional)
116
+
117
+
If you want to rename a model in the picker, pin its `organizationOwner`, or otherwise hand-curate metadata, add it under `models`. The plugin **preserves your entries verbatim** and only injects discovered models whose key isn't already defined:
0 commit comments