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

feat: Custom OPENAI API Host #204

Open
Ashesh3 opened this issue Apr 30, 2023 · 1 comment
Open

feat: Custom OPENAI API Host #204

Ashesh3 opened this issue Apr 30, 2023 · 1 comment
Labels
feature New feature or request pending triage

Comments

@Ashesh3
Copy link

Ashesh3 commented Apr 30, 2023

Feature request

I would like to request the ability to specify a custom OpenAI API Host for aicommits. Currently, aicommits uses the default API Host provided by OpenAI, but it would be useful to be able to specify a different API Host for users who want to use a different OpenAI API endpoint.

Why?

The motivation behind this feature request is that some users may have specific needs or constraints that require them to use a different OpenAI API Host. For example, they may have an on-premises OpenAI API endpoint or they may want to use a third-party provider that offers OpenAI API hosting. Having the ability to specify a custom API Host would allow them to use aicommits with their custom setup.

Alternatives

One alternative solution would be for users to modify the source code of aicommits to support a custom API Host. However, this would require technical expertise and would be difficult for non-technical users.

Additional context

This feature request would be a valuable addition to aicommits, as it would allow users to customize their OpenAI API usage to fit their specific needs. Thank you for considering this feature request.

https://github.com/openai/openai-node/blob/master/dist/configuration.d.ts#L63

@Ashesh3 Ashesh3 added feature New feature or request pending triage labels Apr 30, 2023
@eMUQI
Copy link

eMUQI commented Aug 11, 2023

Same demand

And I also noticed that pull request #232 has been submitted to implement this feature. I would like to kindly request your attention and consideration in reviewing and potentially merging this pull request. Thanks ! @Nutlope @privatenumber

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request pending triage
Projects
None yet
Development

No branches or pull requests

2 participants