Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

[Bug]: The @ lets you selected un supported assistants and throws an error #5558

Closed
1 task done
AFaulkner1990 opened this issue Jan 30, 2025 · 0 comments
Closed
1 task done
Labels
🐛 bug Something isn't working

Comments

@AFaulkner1990
Copy link

What happened?

We have two versions of LibreChat running, one as a general user site that uses ModelSpecs and another power user "admin" site, that lets users create assistants/agents etc.

My assitants config looks like this:

  azureAssistants:
    capabilities: ["code_interpreter", "actions", "tools", "image_vision", "retrieval"]
    disableBuilder: true # Disable Assistants Builder Interface by setting to true
    privateAssistants: false # Enable private assistants by setting to true
    supportedIds: ["asst_xxxxxxxxxxxxx"]
    pollIntervalMs: 3000 # Polling interval for checking assistant updates
    timeoutMs: 180000 # Timeout for assistant operations

"Aila code" is the model spec using azures assistants asst_xxxxxxxxxxxxx

However when I type @ as suggested in the chat input box, it shows all the other assistants, which it then obviously fails if you try and use.

Image

Image

Looking at the code this only seems to be for Admin accounts, I am unsure what you want the expected behaviour to be so have not done a fix

Steps to Reproduce

  • Login as an Admin
  • Create a couple assistants
  • Add only one of them to your supportedIds option
  • Create a ModelSpec using this Id and set disableBuilder to false
  • Type @ into chat input box and see if other assistants show

What browsers are you seeing the problem on?

Chrome

Relevant log output

Screenshots

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@AFaulkner1990 AFaulkner1990 added the 🐛 bug Something isn't working label Jan 30, 2025
Repository owner locked and limited conversation to collaborators Feb 7, 2025
@danny-avila danny-avila converted this issue into discussion #5716 Feb 7, 2025

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
🐛 bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant