librechat.yaml custom endpoints and agent config dont work together

[eroo36]

What happened?

When setting custom endpoints and agents config in librechat.yaml file, custom endpoints are disabled/ignored

If I don't set custom agents config in yaml file and only enable in .env endpoints i can have the custom endpoints and agents with default config

Version Information

efed1c4

Steps to Reproduce

use librechat.yaml file with:

endpoints:
  custom:
    - name: "Perplexity"
      apiKey: "${PERPLEXITY_API_KEY}"
      baseURL: "https://api.perplexity.ai/"
      models:
        default: [
          "sonar-deep-research",
          "sonar-reasoning-pro",
          "sonar-reasoning",
          "sonar-pro",
          "sonar",
          "r1-1776"
          ]
        fetch: false # fetching list of models is not supported
      titleConvo: true
      titleModel: "sonar"
      summarize: false
      summaryModel: "sonar"
      forcePrompt: false
      dropParams: ["stop", "frequency_penalty"]
      modelDisplayLabel: "Perplexity"
  agents:
    recursionLimit: 50
    disableBuilder: false
    capabilities: ["file_search", "actions", "tools", "artifacts", "ocr", "chain"]

What browsers are you seeing the problem on?

No response

Relevant log output

Screenshots

No response

Code of Conduct

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

[danny-avila]

If I don't set custom agents config in yaml file and only enable in .env endpoints i can have the custom endpoints and agents with default config

This is not true, as I use custom endpoints + agents all day everyday.

Please check your logs as instructed here, it's likely a misconfiguration/indentation issue with the YAML:
https://github.com/danny-avila/LibreChat/issues/new?template=BUG-REPORT.yml

[eroo36]

you are right i was getting error log:

"message": "Invalid enum value. Expected 'hide_sequential_outputs' | 'end_after_tools' | 'execute_code' | 'file_search' | 'artifacts' | 'actions' | 'tools' | 'ocr', received 'chain'"

i got the "chain" from the docs, it seems this functionality is new