[Bug] custom model name does not work any more in the latest build version about chatgpt-next-web

[H0llyW00dzZ]

@H0llyW00dzZ Yes.

Currently, initiating a new chat requires either a default system message, a ChatGPT mask, or no system message. Although you can create masks, you must select your preferred one each time.

A proposed solution is to allow users to set a default mask for starting chats, which would be the revised setting Start chats with a default mask [ ].. Users could select their preferred mask from the masks settings, which could include Bard, ChatGPT, or any of their creations like DictionaryGPT. This would prevent the raised issue, as users would write the system message for the default mask themselves.

---

@lizhe2004 It might appear so, but I'm recommending a different implementation for the code that gave rise to this issue. I'm currently using one-api, but I haven't updated my NextChat fork. If I did, I would likely encounter this same problem.

It easy to implement it just like writing a slices byte in go

I might gonna trying it later

[nextchat-manager]

Please follow the issue template to update title and description of your issue.

[H0llyW00dzZ]

At present, custom models for other AI providers are not available, particularly those to which we do not have access (as contributor,devs). It's worth reconsidering how contributors, or any developers for that matter, can address bugs or make improvements to models they cannot access.

[H0llyW00dzZ]

feel free to sponsoring this project as professionalism for example giving they access such as contributor,devs then can easily fix,improve or whatever it is

[lizhe2004]

i use a service named one-api https://github.com/songquanpeng/one-api to convert some 3rd model provider api into openai compatible api, so the qwen model from aliyun dashscope can privide openai format stream response which is accepted by chatgpt next web application.
so I think the issue is not about 3rd AI provider, it is related with that the modelname validation in client side shoud take the custom model list of setting page into consideration rather than only the pre-config DEFAULT_MODELS array. because the custom model name works in eariler version before you add the DEFAULT_MODELS check.

[H0llyW00dzZ]

i use a service named one-api https://github.com/songquanpeng/one-api to convert some 3rd model provider api into openai compatible api, so the qwen model from aliyun dashscope can privide openai format stream response which is accepted by chatgpt next web application. so I think the issue is not about 3rd AI provider, it is related with that the modelname validation in client side shoud take the custom model list of setting page into consideration rather than only the pre-config DEFAULT_MODELS array. because the custom model name works in eariler version before you add the DEFAULT_MODELS check.

that's not actually ai provider so still
At present, custom models for other AI providers are not available, particularly those to which we do not have access (as contributor,devs). It's worth reconsidering how contributors, or any developers for that matter, can address bugs or make improvements to models they cannot access.

[lizhe2004]

sorry to bother you again.
so，how do you think the goal or purpose of such "custom models" configuration in setting page? did i use this by wrong understanding? i think we can use "OpenAI Endpoint " and "Custom Models" the two configuration to support some unkown new model which is compatible with openai api client, so chatgpt-next-web can only focus on openai format.

[H0llyW00dzZ]

sorry to bother you again. so，how do you think the goal or purpose of such "custom models" configuration in setting page? did i use this by wrong understanding? i think we can use "OpenAI Endpoint " and "Custom Models" the two configuration to support some unkown new model which is compatible with openai api client, so chatgpt-next-web can only focus on openai format.

well, still I don't have access to the other ai so what can I do, anyway why should I fix it without testing or anything else when I don't have access lmao

[H0llyW00dzZ]

alternative fix it just disable this inject system prompt since its only for default models such as openai, google ai

[Algorithm5838]

Instead of throwing an error, it should not include a knowledge cutoff date if the date is not explicitly provided.

[H0llyW00dzZ]

explicitly

explicitly better

[Algorithm5838]

I believe a more effective implementation would be to have an option to select a default mask for new chats. This selection could be presented in the settings as 'Start chats with a default mask [ ].' Initially, a default ChatGPT mask might be selected, but users should have the capability to change this.

[H0llyW00dzZ]

I believe a more effective implementation would be to have an option to select a default mask for new chats. This selection could be presented in the settings as 'Start chats with a default mask [ ].' Initially, a default ChatGPT mask might be selected, but users should have the capability to change this.

so Start chats with a default mask [ ]. for example is can be customize by users instead of default chatgpt mask ?

[lizhe2004]

i feel Algorithm5838 and H0llyW00dzZ you are talking about something about mask ,rather than my posted issue.

[Algorithm5838]

@H0llyW00dzZ Yes.

Currently, initiating a new chat requires either a default system message, a ChatGPT mask, or no system message. Although you can create masks, you must select your preferred one each time.

A proposed solution is to allow users to set a default mask for starting chats, which would be the revised setting Start chats with a default mask [ ].. Users could select their preferred mask from the masks settings, which could include Bard, ChatGPT, or any of their creations like DictionaryGPT. This would prevent the raised issue, as users would write the system message for the default mask themselves.

---

@lizhe2004 It might appear so, but I'm recommending a different implementation for the code that gave rise to this issue. I'm currently using one-api, but I haven't updated my NextChat fork. If I did, I would likely encounter this same problem.

[yangbod]

v2.10.1 can use one-api ,after update to v2.10.2, it doesn't work

[fred-bf]

v2.10.1 can use one-api ,after update to v2.10.2, it doesn't work

Please create an individual issue for your question

[fred-bf]

@lizhe2004 could you try the work around in this PR(Preview link)? For the time being, the default system content is set to make OpenAI by default, and the it will be considered to maintain relevant information when registering custom models at server side in the future

#4010

[bbb3n]

i feel Algorithm5838 and H0llyW00dzZ you are talking about something about mask ,rather than my posted issue.

true dude, thats funny
i know what you mean

My solution is to hardcode the model list and set the provider to OpenAI. However, there are still some issues. For example, if I need to set a model with a custom display name, I must use the environment variable CUSTOM_MODEL.

[lizhe2004]

@lizhe2004 could you try the work around in this PR(Preview link)? For the time being, the default system content is set to make OpenAI by default, and the it will be considered to maintain relevant information when registering custom models at server side in the future

#4010

hi，fred-bf ，your demo (Preview link) works for custom model name. great.

[QAbot-zh]

alternative fix it just disable this inject system prompt since its only for default models such as openai, google ai要解决这个问题，只需禁用此注入系统提示，因为它只适用于默认模型，如 openai 和 google ai。

It doesn't work. I disable this inject system prompt, but I still can't get the reply when I try to use non OpenAI and Google model. I use v2.10.1 version.