2025 Roadmap

[danny-avila]

Please share your feedback and thoughts on the 2025 roadmap for LibreChat 🎉

https://www.librechat.ai/blog/2025-02-20_2025_roadmap

[aleibovici]

Hey @danny-avila where is the 2025 roadmap? On the website I can only find the 2024.

[plasticlobster]

https://www.librechat.ai/blog/2025-02-20_2025_roadmap

[danny-avila]

I opened this thread before the blog went live 😅

[marlonka]

Roadmap makes me really excited for 2025, especially the gemini improvements and admin Features will be huge for us. One idea I still have would be some image playground within Librechat that can use Black Forest Labs API to generate and modify like on replicate playground or midjourney edit function.

[ColbySerpa]

MCP Marketplace / Store as seen in Cline & 5ire

There are a few other apps that have this MCP store, like 5ire and most recently Cline. It would make Librechat the leader, given the fork system and everything else in Librechat is so well thought-out.

[dvejsada]

@danny-avila looks great, we are looking forward to all the new features. As our company deployment seems to be quite successful, we will be happy to give LibreChat some publicity sharing our use case;)...

[hamletfg]

As a WebDev and QA Engineer student I've been using Librechat nearly every day. It's been absolutely wonderful having several AI models in one place so a huge thanks to you, Danny and the team for building a great product. I'll be happy to contribute to LibreChat in the future as my skills grow 🙌

[hibukipanim]

Are there plans for supporting OpenAI's new Responses API which will also replace the Assistants API.

From https://openai.com/index/new-tools-for-building-agents/:

Based on developer feedback from the Assistants API beta, we’ve incorporated key improvements into the Responses API, making it more flexible, faster, and easier to use. We’re working to achieve full feature parity between the Assistants and the Responses API, including support for Assistant-like and Thread-like objects, and the Code Interpreter tool. Once this is complete, we plan to formally announce the deprecation of the Assistants API with a target sunset date in mid-2026. Upon deprecation, we will provide a clear migration guide from the Assistants API to the Responses API that allows developers to preserve all their data and migrate their applications. Until we formally announce the deprecation, we will continue delivering new models to the Assistants API. The Responses API represents the future direction for building agents on OpenAI.

Thanks

[danny-avila]

Are there plans for supporting OpenAI's new Responses API

Nope, we have our own agent framework: https://www.librechat.ai/docs/features/agents

[danny-avila]

And Assistants API will officially be deprecated following this announcement

[hibukipanim]

This is disappointing for our use cases, which we started to implement with LibreChat's Assistant API support (while Responses API would make it much easier and nicer).
TL;DR: In our use-case we are interested in implementing the server side of Responses API, and use LibreChat as the conversational UI against it.

The use case is that we develop various services, which internally perform complex LLM-augmented flows using various code frameworks like LangChain, LlamaIndex. These services can expose a conversational API so that users can interact with them from LibreChat. Unlike in the agent framework, the user has no control over which LLM is used (as a combination of them can be used behind the scenes) and which tools are enabled (as the services have this logic internally), and the entry point that handles each new user message is custom code in the service, not directly a specific LLM.
In order for users to be able to converse with such an assistant service using LibreChat, the service needs to implement an API which LibreChat works with. The Completions API is not good enough as it doesn't support streaming events about long-running backend execution, or return files and images. I wrote about it also here #5047 (comment). The Assistants API, while supporting our use-case, is too complex and stateful. The new Responses API seems as a much better fit for an API we'd implement the server side of.

[Lucas-almma]

Danny - Are you referring to OpenAI's deprecation of Assistants, or you are announing LC Assistants will be dreprecated?

[danny-avila]

Both, more info: #6364

[mondo192]

Hi @danny-avila

Can you clarify how the upcoming public cloud hosting will affect the open source self-hosted version? Will any features be restricted or require payment, like the paid API for the code interpreter? Also, will there be any changes to the licensing of the open source version?

Thanks.

[danny-avila]

Good questions!

Basically, the cloud-hosted version will just be the same open-source app you can already self-host. We're not planning to take away or restrict any features from the self-hosted version because of the cloud offering. Everything you can do now for free when self-hosting will stay free. All planned features on the roadmap are planned to be open-source.

The only exception is the Code Interpreter API service – that's already a premium thing, and it'll stay that way.

The cloud version might eventually have some paid tiers (maybe for extra storage, resources, managed stuff, etc.), but the features will mirror what's available in the project repository.

And nope, no plans to change the open-source license of LibreChat (MIT License).