2026 Roadmap

[danny-avila]

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

https://www.librechat.ai/blog/2026-02-18_2026_roadmap

[caramale07]

Amazingly cool project! 🚀 Not sure if you’re already using it, but you might want to check out Deep Agents introduced by LangChain - it could be a great addition.

[rgasper]

All the features on the roadmap sound perfect. Getting librechat to adopt some of the functionality that makes local coding agents so powerful while still being easy to host and easy for nontechnical users to use would be a big win.

[danny-avila]

Exactly my thoughts!

[stam-lab]

Hey Danny, thanks for the roadmap and the continued work on LibreChat. It's a solid offering that keeps getting better with every release!

Now that we're past Q1, I wanted to ask about two items that were called out specifically:

1. Admin Panel - This was a Q1 focus item and has been on the roadmap since 2025. Managing config via YAML and roles without a GUI is a real operational bottleneck. Any updated timeline or is this shifting to Q2/H2?

2. Open-sourcing the Code Interpreter API - The roadmap mentioned this by end of Q1 as the foundation for Agent Skills and Programmatic Tool Calling. Curious where this stands, it's one of the capabilities we're most looking forward to building on.

Totally understand that timelines shift. Just looking for a candid status update so we can plan accordingly. Thanks!

[danny-avila]

On Admin Panel:

Just an update (not April fool's). The v0 iteration of the admin panel is ready, but since this will be under the ClickHouse org, we are waiting on a security review to make public!

From: #3137 (comment)

Open-sourcing the Code Interpreter API

Should be later this month, but not on track for immediate release, as most of my efforts to pick this back up will start mid-month

[michnovka]

Hey @danny-avila , just installed the Admin Panel. I cant believe this is what took over 1 year to be honest... Maybe I installed it wrong, but I cant even manage the users? I see only groups and roles. I can sort of at least display users under the Group Members, but I cant change them. So is there something like a roadmap for the Admin Panel? As at this stage its back to mongoDB direct edits for me... Thanks

[danny-avila]

It did not take 1 year, it took 1 month of freed up available dev cycles to implement, nor is it advertised as feature complete, rather it accomplishes the laid out goals from the roadmap blog as the very first iteration.

I also addressed your other concerns already in the original issue comment, you may have missed it:
#3137 (comment)

[olofmentor]

Good stuff!

Will the group management be integrated with external AD providers?
It would be nice to be able to manage AD groups in an "normal manner" and then be able to change endpoint accesses to users depending on what AD group they belong to.

[danny-avila]

Will the group management be integrated with external AD providers?

AD group sync is already implemented for a while, you may or may not be using already.

https://www.librechat.ai/docs/configuration/authentication/OAuth2-OIDC/azure#advanced-microsoft-graph-api-integration

It would be nice to be able to manage AD groups in an "normal manner" and then be able to change endpoint accesses to users depending on what AD group they belong to.

You can manage groups whether or not synced from AD, and then change endpoint configurations on a group basis.

[olofmentor]

Hi, thank you.
We are using AD groups according to the link you shared. That is for access to librechat, but I have not figured out how to give access to different endpoints depending on AD Group membership.

[Airamhh]

Hello!

@olofmentor - I had the same question, so I opened #12605 for it

To sum it up, the AD groups are not being created in the database when logging in but once this is implemented, the groups should appear over the Admin Panel to configure them

[alfo-dev]

Glad to hear about Admin Panel. Thanks for all your efforts!

One additional question about group sync: Are there plans to integrate non-Microsoft providers like in #10015 or are there any concerns about this approach?

BTW: The 2025 roadmap ist still pinned on top of the discussions - changing it to 2026 might provide more feedback...

[danny-avila]

One additional question about group sync: Are there plans to integrate non-Microsoft providers like in #10015 or are there any concerns about this approach?

I'm happy to merge the PR once it gets updated. Left notes for contributor

BTW: The 2025 roadmap ist still pinned on top of the discussions - changing it to 2026 might provide more feedback...

Thanks, updated.

[Martin-SwDevOp]

Thank a lot for the admin panel Danny, will test asap.

Keep up the good work👍

[jwotzka]

Thanks a lot - very promising!

My admin-panel fails to login. Librechat reports:

`2026-04-14 08:59:38 info: [Login] [Login successful] [Username: admin@example.com] [Request-IP: 10.0.25.162]

2026-04-14 08:59:38 error: ErrorController => error OpenID client is not initialized. Please call setupOpenId first.`

I'm using the latest main branch commits of librechat-admin-panel and librechat itself. Did not have time to investigate.

[Robin-Haupt-1]

I've created a bug report for this: LibreChat-AI/admin-panel#27

[sereikeo]

Folders, spaces, projects, whatever you want to call it.
A way to group chats, and starting a chat from that folder allows it to pick up project specific instructions like links to github, documentation pages, specific versions or limitations of tech stacks, instructions on what not to do.

[dev-fbm]

Thank you very much for all the new features in Q1 2026. However, one thing is still missing – when can users expect to get access to the Code Interpreter?

[wyseowsmu]

Yes, looking forward to the code interpreter! ;)

[danny-avila]

Waiting on my security team to sign off on it, but the repo is ready to be made public so people can start testing!

[smat91]

@danny-avila thank you very much for your great work on LibreChat. I started testing it yesterday and noticed that the API isn't compatible with the current version of LibreChat. LibreChat sends commands to /exec, while the API expects /execute. Did I miss something, or are further adjustments to LibreChat needed to ensure compatibility with the new API?

[danny-avila]

If you're referring to the public API service, it's discontinued, but is now available for self-hosting: https://github.com/ClickHouse/code-interpreter

[smat91]

@danny-avila thank you very much for the fast response. I found the issue. I pointed LibreChat to the wrong endpoint.

[danny-avila]

Writing a new roadmap soon for the next 2 quarters, thanks for your patience on this

[achekroud]

@danny-avila thank you for all your work on librechat <3

i wanted to ask whether your strategy is for librechat to continue serving as the harness, or whether you plan to unbundle the harness (much like you unbundled the models), e.g. allowing users to select harnesses like Pi?