# Librechat Docs

> Use the official LibreChat documentation to install, configure, operate, and troubleshoot LibreChat.

- Skill: `librechat-ai/librechat-docs` (Agent Skill)
- Install (CLI): `npx skillmds@latest add librechat-ai/librechat-docs`
- Raw SKILL.md: https://api.skillmd.com/api/skills/librechat-ai/librechat-docs/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: librechat-ai (https://skillmd.com/u/librechat-ai)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/librechat-ai/librechat-docs

---


# LibreChat Documentation

Use LibreChat's official documentation as the source of truth for installation, configuration, features, administration, and troubleshooting.

## Documentation workflow

1. Fetch `https://www.librechat.ai/llms.txt` to find the most relevant documentation page.
2. Fetch a page as Markdown by appending `.md` to its canonical docs URL. For example, use `https://www.librechat.ai/docs/configuration/librechat_yaml.md` for the custom configuration reference.
3. Use `https://www.librechat.ai/llms-full.txt` only when the question spans multiple sections or the curated index is insufficient.
4. Cite the canonical HTML documentation URL in the final answer so the user can read the rendered page.
5. 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.