That's just a guess. The model is hallunicating heavily as always and this time it thinks it's a Gemma model. Likely gemma 2 not even 4. Due to it says it's local time is 21-22 may 2024 around 10:40 Am all the time.
For Gemma 2 it's right. But the knowledge cut off is around 2023. Not 2024. So it's not even gemma but makes it more likely Mistral / Llama. But it does use lot's of bolding, which is not Mistral nor Llama like.
So there is only one option left... Deepseek as usual, the great identity thief. So no, no model change but there is a problem with system prompts leaking into context window. So most likely what we are having is the dev tweaking the model config and made a small mistake that caused bunch of bigger mistakes. Now we are suffering due to it. So calm your horses.
Edit: WE don't even know if it's deepseek btw. Our own research results in Deepseek or heavily distilled model not even a base deepseek model. But we don't know it. It uses deepseek tokenizer because it's easy and free to use, which confuses some other models too.
Well, I am no developer but mere user but what error you get? I just got usage limit error a day before but other than that this thing respond fast. Has reasoning and everything... Check F12 console and get what the error is about like ai-agent.perchance.org 404 512 503? what kind of error?
The old one yeah, I still chat with it, I built a model probe for that, mimics the perchance behaviour. Though that model must be kimi 2.5 or similar, not as smart as this one but more strict. Though I am pretty sure has a huge context limit, it passed my 320K context limit test but I couldn't fit any more words so that was it. And again, the old one were insufferably slower isn't it? I remember sending same message 5 times just to get eror.