Repository navigation
🔧 fix: Import Path for Custom Configuration Loading - #8319
Merged
Merged
Conversation
… cache instead of reading and parsing the config file everytime a message is saved.
danny-avila
changed the title
danny-avila
approved these changes
Jul 9, 2025
kenshinsamue
pushed a commit
to intelequia/LibreChat
that referenced
this pull request
Aug 4, 2025
xycjscs
pushed a commit
to xycjscs/LibreChat
that referenced
this pull request
Aug 9, 2025
patricksn3ll
pushed a commit
to patricksn3ll/LibreChat
that referenced
this pull request
Dec 11, 2025
jcbartle
pushed a commit
to jcbartle/LibreChat
that referenced
this pull request
May 11, 2026
ThomasVuNguyen
pushed a commit
to ThomasVuNguyen/LibreChat
that referenced
this pull request
Jul 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Update import path for custom configuration loading to use the cache instead of reading and parsing the config file every time a message is saved.
Summary
Both
Conversation.jsandMessage.jsusedloadCustomConfigfunction to retrieve configuration of the app. This resulted in the config file to be read and parsed every time a message is saved, which is not performant and it also caused MCP tool lists to change unpredictably.This fix will make those files get the info from the cache instead.
Change Type
Testing
Run
npm run backendand interact with any LLM model, you will see the config being printed out every a message is sent. This print out is called from theloadCustomConfigfunction.Checklist
Please delete any irrelevant options.