As a Trae Pro annual subscriber, I originally renewed my subscription for one specific promise: “doubling efficiency with the latest global models.” But over the past few months, my experience can be summarized in a single word: slow. Slow model updates, slow response times, and painfully slow official reactions to user demands.

Opening the user feedback section in the Trae Chinese community, it’s clear I’m not an isolated case. Users are directly posting, “Are the models for the global version of Trae no longer being updated? They are generations behind.” Others complain that using the new Grok 4.5 version to edit code only leads to constant errors—features that worked perfectly fine inexplicably break after two version updates. Some users have even noticed that basic UI interactions, like scrolling up through chat history, are broken; the interface forcefully snaps you back to the bottom the moment you try to scroll. Even foundational features like automatic Git commit message generation are failing. These aren’t old complaints; these are fresh posts from just the last few days, proving this isn’t a temporary glitch but an ongoing crisis.

What’s even more disheartening is the refund process. A quick scroll through the feedback section reveals refund requests popping up almost every day or two. Users send emails requesting refunds and receive zero replies. Others accidentally click “Pro+” and get auto-deducted by Alipay, only to have their refund appeals vanish into the void. One user who used Pro+ for four months bluntly stated, “The experience is bad, the models can’t keep up, I want a refund”—and their plea was similarly ignored. When a product’s core competency (model capability) falls behind, and the official team can’t even keep up with basic after-sales support, users’ patience is simply ground away to nothing.

Let me put it bluntly: we didn’t pay an annual fee to buy a “stay tuned” placeholder. We paid for continuously available, up-to-date model capabilities. If Trae genuinely plans to downsize or abandon its global version, then please show the proper attitude—proactively and cleanly issue refunds to your subscribers. Don’t make people chase emails or beg for a reply on Discord. If you can’t do it well, don’t do it at all. But you cannot refuse to update the product while also refusing to issue refunds, leaving your paying users stranded in mid-air.

I know this post carries a lot of heat, but this fire was ignited by every “read but ignored” refund email and every “this version crashed again” update. I hope the official team sees these specific posts in the community and provides a formal, public statement: What exactly is the plan for model updates, and when will the refund process actually work?

Users have never asked for much—we just want you to keep your word.