LibreChat Removal Vision
Vision
With the “Migrate to uvilo-mono” project implemented, LibreChat is no longer part of Forge’s stack. This project ensures a clean break by verifying the migration’s success criteria are met and removing all residual references to LibreChat, deprecated tooling, and obsolete skills from Persistent Knowledge.
Background
The “Migrate to uvilo-mono” project defined 6 success criteria (V0–V5) for replacing LibreChat with uvilo-mono. Before removing LibreChat references, we must verify those criteria are fulfilled. Then we must audit all Persistent Knowledge — Knowledge, Skills, Prompts, and Guides — for references to LibreChat, forge-spawn, and other tooling that depended on the old stack.
Research Instructions
Do not assume the new environment’s capabilities. If a reference cannot be verified against the current uvilo-mono stack, flag it for human review rather than deleting or rewriting it.
Requirements
R1: Verify Migration Success Criteria
Verify that all 6 success criteria from the “Migrate to uvilo-mono” Vision (V0–V5) are fulfilled: LibreChat removed from stack, all agents as uvilo-mono Bots, all MCP servers attached, sub-agent spawning works, model override works, API-key auth works.
R2: Remove LibreChat References from Persistent Knowledge
Audit and clean all Persistent Knowledge (Knowledge files, Skills, Prompts, Guides) of references to LibreChat, LibreChat-specific configurations, and deprecated tooling (e.g., forge-spawn’s LibreChat dependency, LibreChat agent definitions, LibreChat YAML configs).
R3: Remove Obsolete Skills and Configs
Identify and remove or archive any Skills, MCP server configs, and infrastructure files that are specific to LibreChat and no longer functional in the uvilo-mono environment.
R4: No Assumptions About New Environment
Every change must be verified against the current uvilo-mono stack. If a reference’s status is uncertain (e.g., a skill that might still work but hasn’t been tested), flag it for human review rather than assuming it works or doesn’t.
Success Criteria
| # | Criterion | Measured by |
|---|---|---|
| V1 | All 6 migration success criteria verified | Each V0–V5 from Migrate_to_uvilo-mono Vision confirmed or flagged |
| V2 | No LibreChat references remain in published Knowledge | grep -ri "librechat" --include="*.md" returns zero hits on published files |
| V3 | No LibreChat-specific Skills or configs remain in active directories | forge-spawn, LibreChat_Service, and related configs removed or archived |
| V4 | All uncertain references flagged for human review | Items that can’t be verified are listed, not silently removed |
Out Of Scope
- Re-implementing any features that were lost in the migration
- Changes to the uvilo-mono codebase itself
- Archiving the Migrate_to_uvilo-mono project (separate task)