Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhancement: Granular Plugin Control #1625

Open
1 task done
paychex-ssmithrand opened this issue Jan 24, 2024 · 1 comment
Open
1 task done

Enhancement: Granular Plugin Control #1625

paychex-ssmithrand opened this issue Jan 24, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@paychex-ssmithrand
Copy link

What features would you like to see added?

It would be nice for an enterprise deployment to be able to control a list of allowed plugins without codebase modification (for those who fork the public repository).

More details

A number of plugin definitions are included in LibreChat's codebase. We'd rather not create drift between the upstream LibreChat codebase and our Fork by deleting plugin definitions.

Which components are impacted by your request?

Plugins

Pictures

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@paychex-ssmithrand paychex-ssmithrand added the enhancement New feature or request label Jan 24, 2024
@danny-avila
Copy link
Owner

Understandable! This is planned along with granular user access control in general.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants