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

Knowledge - Able to chat with deleted knowledge files in existing threads. #519

Open
sangee2004 opened this issue Sep 16, 2024 · 2 comments
Labels
bug Something isn't working knowledge

Comments

@sangee2004
Copy link

Electron build - d27f9f

Steps to reproduce the problem:

  1. Create an assistant
  2. Add multiple (at least 2) knowledge file say file1 and file2 using "Add Local Files"
  3. Chat with the assistant about one of knowledge file say file1.
  4. Edit the assistant and remove file1.
  5. Start a new chat with the assistant about the delete knowledge file -file1. This will not be able to fetch any information as expected
  6. Continue to chat in existing thread (from step3) about delete knowledge file .

User will continue to get information about the deleted knowledge file.

Expected Behavior:
User should not get any information about the deleted knowledge file even in existing threads.

@sangee2004 sangee2004 added bug Something isn't working knowledge labels Sep 16, 2024
@cjellick
Copy link
Contributor

Is the information coming from queries to the knowlege api or from the context that had been built up? If it's from the context that's been built-up, then thats expected

@sangee2004
Copy link
Author

sangee2004 commented Sep 17, 2024

When I tested the same scenario again, I was not getting the information from the deleted knowledge files when tool call was made to knowledgeRetrieval tool.
When I see the behavior mentioned in the issue , it is from the Knowledge Retrieval Context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working knowledge
Projects
None yet
Development

No branches or pull requests

2 participants