librechat.yaml.
Setup
Add Opper underendpoints.custom:
.env and restart:
fetch: true makes LibreChat pull the catalog from GET /v3/compat/models at startup, so the picker fills itself. Set it to false and rely on models.default if you’d rather pin an explicit list.
Use the
${VAR} env-var syntax rather than pasting the key into librechat.yaml — the file is usually committed alongside your deployment.Choosing a model
Withfetch: true, LibreChat lists everything your key can reach, filtered by your model access rules. The catalog is large, so a curated models.default list is often the nicer experience for end users.
Multi-user usage
LibreChat is typically multi-tenant. Forward per-user tags with theX-Opper-Tags header to break usage down by user or workspace in Opper analytics — see Tags and usage attribution.
Troubleshooting
The endpoint doesn't appear
The endpoint doesn't appear
LibreChat reads
librechat.yaml at startup only. Restart the container or process after editing it.The model list is huge
The model list is huge
Set
fetch: false and list the models you want in models.default.Related
Tags and usage attribution
Split usage per user or workspace.
Open WebUI
The other self-hosted chat workspace.