Support for privateGPT, including support for RAG functions like rspecting context and parsing of sources #312
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi, as suggested in our recent discussion #305, here's a PR that adds support for interacting with privateGPT. Its based on the openai-backend, with some additions. The focus was to enable the use of two specific key words, as described in the API reference:
use_context
: directs the LLM to use the context of documents that have been "ingested"include_sources
: directs the LLM to also return information about the sources of the context (so far: file name and page number, if appropriate).I changed the code of
gptel-openai.el
to send the additional keywords to the llm server, and to correctly parse the answer if sources are provided.I tested the code with different queries, and so far it works for my use case. However, there is at least one missing feature: currently, the two new keywords
use_context
andinclude_sources
are hardcoded tot
. It would probably be better to make them configurable when creating the backend. Unfortunately, I'm not sure how to do that correctly.