danny-avila/LibreChat

Choose this fork if you want a near-upstream LibreChat base with a narrow abort-handling tweak. Choose upstream instead if you want the newest feature set, especially recent MCP/auth/admin work and broader current maintenance.

Prefer this fork only if you specifically need its older plugin-era behavior and are prepared to maintain it yourself. For most adopters, upstream is the better base because it is far more active and materially more capable.

Choose this fork if you need organization-specific chat platform behavior and are willing to manage upstream drift. Stick with upstream if you want the broadest feature velocity and lowest maintenance burden.

Choose this fork only if you want a simpler, older chat-focused codebase and can live without the modern LibreChat platform features. If you want agents, MCP, multi-provider breadth, code execution, or active maintenance, upstream is the better choice.

Prefer this fork only if you want a near-upstream LibreChat copy and are comfortable carrying the 18-commit lag yourself. If you want added capability or faster access to current upstream fixes, upstream looks safer.

Prefer this fork if you need tenant-aware admin workflows and are comfortable owning a large divergence. Prefer upstream if you want the newest agents, MCP, provider support, and recent fixes with less maintenance burden.

Choose this fork if you want a customized LibreChat branch and can tolerate upgrade debt. Avoid it if you need upstream parity, especially for newer agent, artifacts, or admin work.

Prefer this fork only if you want the narrow, older ChatGPT-clone behavior and do not need LibreChat's modern multi-provider, agent, tool, and admin platform. For most adopters, upstream is the better base.

Choose this fork if you want a more customized LibreChat deployment with tenant-aware auth, richer admin/workflow tooling, and you are comfortable carrying a sizable upstream delta. Choose upstream if you want the broadest compatibility and the freshest fixes.