feat: add support for custom OpenAI base URLs (AEGHB-450) #310
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
github-actions
bot
changed the title
|
@sammcj Thanks for your contribution. custom OpenAI base URL is a useful feature to support other LLMs, I will cherry-pick your commit and merge it |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR is intended to add support for providing a custom OpenAI compatible API endpoint.
Many LLM servers people run locally or within their network can expose an OpenAI compatible API, as such you usually update the "base url" to point to your server.
Examples of such projects include the popular:
There’s also integration libraries like LiteLLM which basically means any project that uses it automatically gets an openAI compatible API: BerriAI/litellm
Please do verify my logic as I am not experienced with C and as such relied on a LLM to assist me in making this change.
I believe this change is required to support espressif/esp-box#110
Thank you for your consideration.