You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When I go to the history, these reports are not available for further queries. When a report is immediately finished being written GPTR does allow query for a period (although this seems to be for a limited time?
Also, after a report has been produced, it seems like that is the perfect time to improve focus and style and ask for further research or for rewriting.
Describe the solution you'd like
Could embeddings per report be kept until a delete request or alternatively for a period defined as a parameter?
Then, either when accessed as a historical report or after the first iteration of the report, allow for further query or further research or for rewriting.
Describe alternatives you've considered
I'm not sure there is a good alternative other than feeding a finished report in to a hybrid search, but the loss of the original search and embeddings limits the usefulness of this.
The text was updated successfully, but these errors were encountered:
a) True - High Level, the documents are embedded into a Langchain Vector Store on every run
We'll probably want to add support for a Vector Store like Pinecone or Mongo to preload the data into the Vector Store and run a report with that Vector Store as Context
c) I like the idea of maintaining as much context for as long as possible within reason - I'd even go one step further to say that I would love for the project to have an advanced memory module.
For example, Langgraph put out this memory agent which is able to classify any chat inputs as:
About the User
Tracking To Dos of the user
How the user likes things done
That could be huge in terms of personalization for the app where the memory module keeps track of: what you do for a living, what's your areas of interest, why you're interested in it, how far along you are in your education of a specific topic...
d) For A-C above: Green light for the PR if someone would like to start investigating or start building it out
Is your feature request related to a problem? Please describe.
When I go to the history, these reports are not available for further queries. When a report is immediately finished being written GPTR does allow query for a period (although this seems to be for a limited time?
Also, after a report has been produced, it seems like that is the perfect time to improve focus and style and ask for further research or for rewriting.
Describe the solution you'd like
Could embeddings per report be kept until a delete request or alternatively for a period defined as a parameter?
Then, either when accessed as a historical report or after the first iteration of the report, allow for further query or further research or for rewriting.
Describe alternatives you've considered
I'm not sure there is a good alternative other than feeding a finished report in to a hybrid search, but the loss of the original search and embeddings limits the usefulness of this.
The text was updated successfully, but these errors were encountered: