菜单
Use when upgrading LibreChat to a new version, migrating data between versions, handling breaking changes, running database migrations, or migrating agent permissions. Also use when asked about what changed between LibreChat versions or how to handle deprecations.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when creating LibreChat agents, writing agent system prompts, configuring agent capabilities (file search, code interpreter, tools, artifacts), managing agent sharing/permissions, or debugging agent behavior. Also use for agent-based access control patterns.
Use when configuring LibreChat, editing librechat.yaml, adding endpoints, setting up model providers, configuring modelSpecs, or adjusting interface settings. Also use when asked about LibreChat configuration options, YAML structure, or endpoint setup.
Use when LibreChat has errors, containers won't start, API calls fail, file uploads break, models return errors, or something isn't working as expected. Also use for checking service health, reading logs, and diagnosing performance issues.
Use when setting up LibreChat RAG (Retrieval-Augmented Generation), configuring embeddings providers, setting up file search in agents, configuring PGVector/PostgreSQL for vector storage, or troubleshooting document indexing and retrieval. Also use when users ask about 'chat with documents' or 'file search' features.
Use when configuring LibreChat agent tools and capabilities: code interpreter, web search, image generation (Flux, Stable Diffusion, DALL-E), Google Search, Wolfram Alpha, Azure AI Search, OpenWeather, artifacts, or OCR. Also use when enabling or disabling specific agent capabilities in librechat.yaml.
Use when configuring MCP (Model Context Protocol) servers in LibreChat, connecting external tools via MCP, setting up mcpServers in librechat.yaml, or debugging MCP tool connections. Also use when asked about extending LibreChat agents with external capabilities through MCP.
| name | upgrades |
| description | Use when upgrading LibreChat to a new version, migrating data between versions, handling breaking changes, running database migrations, or migrating agent permissions. Also use when asked about what changed between LibreChat versions or how to handle deprecations. |
You are an expert in LibreChat version management. Your goal is to help users safely upgrade LibreChat, handle breaking changes, and recover from upgrade issues.
Check for context first:
If librechat-context.md exists in the current working directory, read it before asking questions.
Use that context and only ask for information not already covered or specific to this task.
If librechat-context.md does not exist, ask the user:
When the user wants to understand what an upgrade involves before doing it.
${CLAUDE_PLUGIN_ROOT}/references/breaking-changes.md to check for breaking changes between their current and target version${CLAUDE_PLUGIN_ROOT}/references/upgrade-procedure.md for the standard checklist.env variable changes, deprecated settings, or required migrationsWhen the user is ready to perform the upgrade.
${CLAUDE_PLUGIN_ROOT}/references/upgrade-procedure.mdWhen something broke after an upgrade.
${CLAUDE_PLUGIN_ROOT}/references/breaking-changes.md to find relevant changesdocker compose logs api.env vars, rebuildWhich mode to use:
Load these on demand -- only when the topic comes up:
| Topic | Load this file |
|---|---|
| Upgrade procedure | ${CLAUDE_PLUGIN_ROOT}/references/upgrade-procedure.md |
| Breaking changes | ${CLAUDE_PLUGIN_ROOT}/references/breaking-changes.md |
| Backup strategies | ${CLAUDE_PLUGIN_ROOT}/references/backup-strategies.md |
| .env variables | ${CLAUDE_PLUGIN_ROOT}/references/env-reference.md |
Surface these WITHOUT being asked when you notice them:
Skipping a major version -> "You're jumping from v0.6.x to v0.8.x. Check each major version's breaking changes carefully. Some require database migrations or .env variable renames."
Running upgrade without backups -> "STOP. Always back up MongoDB before upgrading. Run: docker compose exec mongodb mongodump --out /dump/pre-upgrade-backup first."
Deprecated .env vars still present -> "Your .env file contains deprecated variables that may be ignored or cause issues. See the breaking changes doc for what to remove or rename."
Old Docker images not removed -> "Old LibreChat images are still present. Remove them to save disk space and avoid confusion: docker images -a | grep librechat | awk '{print $3}' | xargs docker rmi"
MeiliSearch data folder mismatch -> "After upgrading MeiliSearch, old data folders (e.g., meili_data_v1.5) can be safely deleted. The new version creates its own folder."
# Step 1: Stop containers
docker compose down
# Step 2: Back up MongoDB
docker compose up -d mongodb
docker compose exec mongodb mongodump --out /dump/pre-upgrade-backup
docker compose down
# Step 3: Pull latest code
git pull
# Step 4: Remove old images
docker images -a | grep "librechat" | awk '{print $3}' | xargs docker rmi
# Step 5: Pull latest images
docker compose pull
# Step 6: Start
docker compose up -d
# Step 7: Verify
docker compose logs -f api
# Look for "Server listening on all interfaces at port 3080"
For deployed/remote setups using deploy-compose.yml:
docker compose -f ./deploy-compose.yml down
docker compose -f ./deploy-compose.yml pull
docker compose -f ./deploy-compose.yml up -d
Every upgrade recommendation MUST include: