Slow requests hold up to the point where they are no longer usable

The application worked very well at first.
For some reason, over time, he should have become better and smarter, but you taught him more cunning.
Slow requests work very well in the free version, but when the pro version is finished, for some reason slow requests do not respond at all.

He’s constantly pushing you to buy and slow requests why did you remove the countdown timer.

If the requests are limited, why does he corrupt the code he wrote properly? Is it to cause us to send unnecessary requests?

cloude-3-5-sonnet
While it used to work like a superior intelligence, now it’s nonsense.
The most interesting part is that the upper version is only terrible in writing good code in design. I have never seen anyone write code that works properly. I print the codes with version 3.5 and I use the upper version for design.

What I don’t understand is why the artificial intelligence, which previously gave good answers, now confuses the things it knows.

Isn’t 500 requests too few for an artificial intelligence model that constantly writes complex code?

There is no special logic that writes “corrupt code” for slow requests.

Slow requests function the same as fast requests, they just have increased latency.

What I don’t understand is why the artificial intelligence, which previously gave good answers, now confuses the things it knows.

Could you provide some examples?

1 Like

priority advance chat history
No chat history after switching to pro
Previously, my chats were visible in the past section, but now they are not.

Slow requests, times change all the time, and when the chat history is more than 2 or 4 days, there are crashes, it closes on its own and starts from scratch.

example TIC –TAC-TOE
You make the game, it creates the files, the structure, the logic, it all sets up, but when you make an error in the middle of the project, you forget the old code structure, you always write new codes, and when you don’t realize this, you get into an error deadlock.

in simpler words

function familyName($fname, $year) {
  echo "$fname Refsnes. Born in $year <br>";
}

familyName("Hege", "1975");

Let’s say he used the above function in the project. After some time has passed, when he needs it, he doesn’t use it, he creates a new one.

function Name($fname, $year) {
  echo "$fname Refsnes. Born in $year <br>";
}

Name("Hege","1975");

I hope I could explain

This sounds like a bug, and you should report it. Chat history should be visible.

For the rest, I’ll repeat: there is no special logic that writes “corrupt code” for slow requests.

I understand you, but you do realize that this is a commercial service, right?

Chat history is not visible only in claude-3.5-sonnet and higher versions, other models are visible.