Turbo doesn't save conversation ID.

[romerocox]

I have noticed that when using the Turbo feature with the official API, GPT creates a new instance of the chat with every message sent. Is there any intention to make the Turbo feature work with the API method, just as it does with the non-API method?

I had been using the non-API method, but I started receiving errors, so I switched to the official API method, which is when I realized the issue I mentioned above.

Thank you in advance for your help and excellent work.

[romerocox]

[alexz006]

I have noticed that when using the Turbo feature with the official API, GPT creates a new instance of the chat with every message sent. Is there any intention to make the Turbo feature work with the API method, just as it does with the non-API method?

I had been using the non-API method, but I started receiving errors, so I switched to the official API method, which is when I realized the issue I mentioned above.

Thank you in advance for your help and excellent work.

To work in dialog mode in the official API, you need to send previous messages each time, for example:

$data = [
  //...
  "messages" => [
    ["role" => "user", "content" => 'your previous message'],
    ["role" => "assistant", "content" => 'response to your previous message'],
    ["role" => "user", "content" => 'your new message'],
  ],
  //...
];

Thus, if a lot of text is sent, you will be able to reach the limit of available tokens..

This error most likely indicates that the chat was modified through the web interface of chat.openai.com. Before sending the first message through an unofficial API, clear the conversationId field - this will start a new chat.

[romerocox]

Thanks for clarifying. I wonder if it is possible to use the API method with the regular 3.5 dialog mode.