LibreChat Documentation
Use LibreChat's official documentation as the source of truth for installation, configuration, features, administration, and troubleshooting.
Documentation workflow
- Fetch
https://www.librechat.ai/llms.txtto find the most relevant documentation page. - Fetch a page as Markdown by appending
.mdto its canonical docs URL. For example, usehttps://www.librechat.ai/docs/configuration/librechat_yaml.mdfor the custom configuration reference. - Use
https://www.librechat.ai/llms-full.txtonly when the question spans multiple sections or the curated index is insufficient. - Cite the canonical HTML documentation URL in the final answer so the user can read the rendered page.
- Check the changelog when behavior may differ between LibreChat releases.
Accuracy and safety
- Do not invent configuration keys, environment variables, commands, defaults, or supported integrations.
- Preserve the exact spelling and casing of settings shown in the documentation.
- Distinguish settings in
.env,librechat.yaml, Docker Compose overrides, and provider dashboards. - Use placeholders for credentials and secrets. Never ask users to publish secret values.
- If the documentation does not answer the question, say so and direct the user to the LibreChat GitHub discussions or issue tracker.