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

Support a way to define default model from CUSTOM_MODELS env. #3961

Closed
wants to merge 1 commit into from

Conversation

jalr4ever
Copy link
Contributor

What's new

Define a default model

To define a default model, simply add a +* prefix to CUSTOM_MODELS item. The first model to receive this prefix will become the new chat default model.

Each new chat window will use the default model, but old windows that have already changed the model will not be affected by this.

Usage

For example, gpt-4-1106-preview will be default model:

docker pull jalr4ever/chatgpt-next-web

docker run -d -p 3000:3000 \
   -e OPENAI_API_KEY=sk-xxxx \
   -e CODE=your-password \
   -e CUSTOM_MODELS=-all,+*gpt-4-1106-preview,+gpt-3.5-turbo,+gpt-3.5-turbo-0613,+gpt-4-0125-preview \
   jalr4ever/chatgpt-next-web

Copy link

vercel bot commented Jan 31, 2024

@jalr4ever is attempting to deploy a commit to the NextChat Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Contributor

Your build has completed!

Preview deployment

@wxupjack
Copy link

wxupjack commented Mar 6, 2024

How is this pull request going? This is a valuable feature.

@jalr4ever
Copy link
Contributor Author

@fred-bf Hi, fred-bf. As a maintainer of this project, what do you think of this feature support? Can you help to review and merge this request?

@Dean-YZG
Copy link
Contributor

Thanks for the contribution,but it would be better to apply a new env var to sign the default env

@jalr4ever
Copy link
Contributor Author

Thanks for the contribution,but it would be better to apply a new env var to sign the default env

Closed. It's now moved to another PR, see: #4545

@jalr4ever jalr4ever closed this Apr 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants