[Feature]: Save queries and their embeddings #1099
Description
Contact Details
No response
What should we build?
Currently embeddings are encoded in the cursor which works but is not ideal as the payload is very big and we lose this cursor between different sources.
For example when an agent constructs a query, injects context and returns an answer , we might want to return this query, so the frontend can do a separate call to show these results to avoid streaming all the data over the agent route (#1083)
Additionally we can unlock new potential where we may show recent queries to users, save embedding API calls, do analysis on used queries etc...