LibreChat Removal Spec
All LibreChat references, deprecated tooling, and obsolete skills are removed from Persistent Knowledge. The Forge knowledge base and skill set accurately reflect the current uvilo-mono / forgentic runtime, with no residual references to the former LibreChat stack.
1. Migration Success Criteria Verified
All 6 success criteria from the “Migrate to uvilo-mono” Vision (V0–V5) are confirmed as fulfilled. LibreChat is not part of the runtime stack. This verification is documented and does not require ongoing maintenance.
2. Knowledge Files Updated
All published Knowledge files in the Forge department describe the current uvilo-mono / forgentic architecture exclusively. There are no references to LibreChat, librechat.yaml, forge-spawn, LibreChat agent definitions, or LibreChat deployment procedures.
Specifically:
- Forge_Setup.md describes deploying uvilo-mono (bot-craft) on Railway, not LibreChat.
- Forge_Infrastructure.md shows the current service architecture with uvilo-mono as the runtime, not LibreChat.
- Forge_Agent_Architecture.md describes the Bot model, not LibreChat agent definitions, ModelSpecs, or sync scripts.
- Forge_Agent_Orchestration.md describes the orchestrator → uvilo-mono execution path, not forge-spawn or LibreChat conversation transcripts.
- Forge_Agents_User_Guide.md references the current Bot system and tooling, not forge-spawn,
librechat.yaml, or LibreChat chat history. - Forge/README.md has no LibreChat references.
3. Obsolete Skills Archived
The MongoDB skill is archived. MongoDB was part of the LibreChat stack and is no longer in use.
4. In-Scope Skills Updated
The following published Skills reference LibreChat-era infrastructure and are updated to reflect the current environment:
| Skill | What Changes |
|---|---|
| MCP_Development | References to “for LibreChat”, LibreChat Docker image, and LibreChat container npx behavior are replaced with uvilo-mono / forgentic equivalents. |
| Verify_Infrastructure | References to restarting LibreChat are replaced with current infrastructure restart procedures. |
| Playwright_MCP | References to librechat.uvilo.ai navigation and /workspace/librechat/.secrets for credentials are replaced with current URLs and env-var-based credential access. |
| Typesense_MCP | Reference to “No curl in LibreChat container” is replaced — curl is available via forge-bash__run. |
| Build_Typescript | Reference to restarting LibreChat is replaced with current runtime restart. |
| Git_Dashboard | Reference to /workspace/librechat/.secrets is replaced with env-var-based credential access. |
| Preview | References to /workspace/librechat/.secrets for Vercel bypass token are replaced with env-var-based access. |
| Update_Infrastructure/references/infrastructure_state.md | LibreChat service ID, images, and volume info are removed; replaced with current infrastructure state. |
Out-of-Scope Skills
Vercel_MCP, Linear_MCP, and Suprsend_MCP are out of scope. They will be replaced later (likely via Composio) and are not updated in this project.
5. Credential and Configuration Model
All credential references across in-scope Skills point to environment variables on the forgentic container, not to /workspace/librechat/.secrets or librechat.yaml. No Skill references librechat.yaml as a configuration source.
6. Container Environment Model
All references to the “LibreChat container” are replaced with the forgentic container on Railway. Shell commands (bash, curl, etc.) are invoked via forge-bash__run, not executed directly inside a LibreChat container.
7. Obsolete Files and Directories Removed
The following LibreChat-specific files and directories no longer exist in the repo:
Forge/Configs/LibreChat_Service/(librechat.yaml, Dockerfile.librechat, startup.sh)Forge/Configs/MCP_Servers/forge-spawn/(old forge-spawn MCP server source)Forge/Assets/LibreChat_Agent_Instructions.mdForge/Assets/LibreChat_Artifact_Instructions.mdForge/Assets/LibreChat_MCP_Server_Instructions.md
8. Verification Clean
A grep -ri "librechat" --include="*.md" on all published files returns zero hits. No LibreChat references remain in active, published Persistent Knowledge.