Enhancement: Custom Plugins (Langchain Tools) as External Modules - Dependency Injection

[MoezGholami]

What features would you like to see added?

With the current implementation of plugins, adding any custom plugin will require changing the project code. Let's make the plugins external dependencies.

More details

According to the documents (make_your_own.md), adding a new plugin to Librechat requires modifying the repository files including handle_tools.js, index.js, and manifest.json.

If anyone wants to implement their own plugin, they have to fork the repository and manually keep up with the updates, git conflicts, and breaking changes.

An alternative approach would be having Librechat to look for external Langchain tools and do the imports/exports automatically (specially once manifest.json goes away).

Which components are impacted by your request?

No response

Pictures

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[MoezGholami]

Honestly, I can't think of any clean way to implement this.

[danny-avila]

Honestly, I can't think of any clean way to implement this.

I've thought a lot about this and know of a way, but I want to retire the old way of handling plugins and build it from the ground up anyway. I would implement this first for Assistants, then a new agent system that is also compatible with other endpoints (Anthropic, google, etc.)

[danny-avila]

The Assistants endpoint is most of the way there for dependency injection of tools.