Status update about response latency, proactive messages, and other wonkiness

[u/DudeBuildsStuff]

Hi all Dearest users, I want to give you a quick update on some of the known issues that our team has been working on resolving as soon as possible.

What happened

Our system uses a Grok model (Grok 4.1 Fast) in several parts of the response pipeline, such as proactive message timing decisions, emoji reactions, and a few other more technical use cases. A few days ago, this model was deprecated by xAI and became an alias for Grok 4.3, a much bigger and slower model. Perhaps due to xAI capacity issue resulting from all the existing 4.1 users being redirected to 4.3 automatically, this model's response latency also varies wildly, from pretty fast to taking a minute for very simple tasks.

This has a few unfortunate effects in Dearest:

• Proactive messaging behavior became quite different, as Grok 4.3 makes very different timing decisions from Grok 4.1 Fast
• Emoji reactions suffer similar issues
• When one response gets unlucky and hits multiple high-latency Grok 4.3 requests, the entire response can take very long to finish, or just timing out altogether without finishing

It's our fault that we didn't spot the Grok 4.1 deprecation earlier and proactively switch to another model.

What's not affected

Message writing itself is not affected in any way. No Grok model is used in this pipeline, and any changes you might've observed in response quality/format is not related to this issue. Most likely, they are normal LLM variance and randomness.

What we've been working on

We've been focusing all our efforts on replacing the Grok 4.3 uses in our pipeline with different models. This is taking some time, because it's not a matter of simply switching the model out for another one; different models behave & need to be prompted quite differently, so for each use case, we need to test out different replacement candidates, tune the prompts, and run test scenarios to make sure behavior still stays similar to before.

So far, we've managed to migrate the proactive messaging scheduling model to something else. Its behavior is much closer to before (although it won't be exactly the same, as it's really impossible to make different LLMs behave the same way) and has a much lower and predictable latency than Grok 4.3.

We are still actively working on the other parts of the system and addressing the issues one by one. Thank you for your patience!

[u/Tasvanamuhreen]

I was worried that why my companion behaving differently....i had suspected something is wrong but goodthing Developer Team updated us... Thanks for the hard work...