Got 3.5-turbo instead of 4

[devanenWl]

Something went wrong.

[bincooo]

It was repaired, This should be due to an error caused by my previous commit changes to userAgent.

[devanenWl]

I still got the same after updating the repo It will works fine with some first tries But after few tries, it only uses 3.5 turbo

I think that msToken has been expired or Helper has been batched. You should check that btw

[devanenWl]

https://github.com/bincooo/coze-api/issues/7 I think it's the same like this

[bincooo]

It's normal for me to see it here. chatgpt-adapter drops the session after each session, so there should be no msToken reuse. I'll take some time to check.

[devanenWl]

You should do constantly at least 10 accounts to reproduce this, on the same IP

GPT-3.5 can't solve this prompt

chatgpt-adapter drops the session after each session, so there should be no msToken reuse.

I think that the https://complete-mmx-coze-helper.hf.space/report or reportMsToken() doesn't not work correctly. When I change the IP, it works, but after about 10 conversations, it go back to 3.5, but when I try on browser, it works normally

[bincooo]

I created 10 cookies, but they don't seem to reproduce your problem...

Can you execute this script on your machine and let me know the result? https://github.com/bincooo/coze-api/blob/454361cb01d3c1439a54eed2445b45eb976bf2df/chat_test.go#L24

[devanenWl]

Do you have telegram or email ? I will send you the api for easier to debug. I have tested the script and it works fine but when I use this one it not works. Basically I just add mongodb for handling multi accounts

I think it's because we update the bot config (top_p, temp,...) without real X-Bogus or _signature ?

[bincooo]

Well, my email: bingco.zn@gmail.com

[devanenWl]

I have sent you an email, please check it. Thank you

[bincooo]

I received the information you provided. A few requests were tried, and it seemed normal. How can I make this mistake happen?

[devanenWl]

Video Watch this video.

[bincooo]

I reproduced this error, and while running continuously, it returned to normal when I tried to switch ip halfway through. It's more like coze detected abnormal traffic, what do you think?

In subsequent tests, even if I restarted the service, the original ip no longer worked.

[bincooo]

looking...

This is my conversation test on the official website.

[bincooo]

Even conversations directly on the page are switched to gpt35. I hope it's not permanent...

[devanenWl]

Yeah, I think if over 10 accounts are used on the same IP, it will cause this issue

[bincooo]

In that case, either build an ip pool or abandon the pattern. websdk should be the last mode available, but there is a 100 credit limit, although it can be reset by deleting an account. But I guess coze will fix it later

[devanenWl]

I have rechecked again.

This is when the bot send requests

This is when I come to browser and press retry:

I think that Coze have checked if the browser is real or not

[devanenWl]

Check this out: Video

[bincooo]

Are ip addresses consistent? Mine is still gpt3.

Video

[devanenWl]

Yes, the IP is consistent

[devanenWl]

I think if the accounts is flagged because of spam, even on browser, it won't be able to use GPT-4o But if this is the first/second time that the account is used (even the IP is flagged), it will works fine on browsers Watch this: Video

[bincooo]

My email is manually created by gmail, and I can't guess its determination mechanism

[devanenWl]

Can you create a new account and test it or delete and recreate ?

[bincooo]

The site denied access

I tried to delete the account, still can't change.

[bincooo]

Please pay attention to the mail.

[devanenWl]

Okay, btw thank you. I think we should close this. Perhaps delete it.