The Ghost of Intelligent Assistance

It started so promisingly, you know? I’d snagged a deal on the Beta version—a generous offer, considering the integrated large language models like Claude and ChatGPT were included at purchase. They were a godsend, honestly. Just a quick prompt, a few carefully worded instructions, and bam—code that actually made sense.

I was cranking out projects at a pace I hadn’t experienced in years. It felt…intuitive. Then, the updates rolled in. Subtle at first, a few minor tweaks here and there.

But then—poof—the LLMs were gone. Just…gone. It’s like ByteDance quietly pulled the plug, leaving me staring at a shell of an IDE. The telemetry continues, of course—a fact that’s particularly galling. Why do they need to track everything? Seriously, it’s a bit much.

I spent a ridiculous amount of time digging through the settings, trying to find a way to disable it. The documentation was frustratingly vague, offering only cryptic suggestions and dead ends. It’s a classic case of “move the goalposts,” isn’t it? They sell you a feature, then yank it away without a word. You’re left scratching your head.

The Reddit Echo Chamber

I wasn’t alone in my frustration. The online chatter—specifically on Reddit—is a swirling vortex of disappointment and anger. The r/chatgptcoding subreddit is practically ablaze with complaints. People are sharing screenshots of the interface, detailing the abrupt removal of the LLM support. It’s a digital town square of bewilderment.

Seriously, who does that?—It’s a shockingly common tactic.

One user, a young programmer named Liam, succinctly put it: “Trae was brilliant until they decided to monetize the intelligence.” Another, a seasoned developer named Sarah, added, “I feel like I bought a Ferrari and they handed me a go-kart.” The sentiment is overwhelmingly negative. It’s a testament to the fact that people genuinely valued that integrated assistance. You know, it’s about more than just the code; it’s about the support.

The Year in LLMs—and the Erosion of Trust

Looking back, 2025 was a pivotal year for large language models. The technology was evolving at a breakneck pace, and Trae seemed to be riding that wave—until it wasn’t. Simon Willison’s annual review—a surprisingly insightful piece—highlights the rapid advancements and the growing anxieties surrounding data privacy and algorithmic control. (By the way…) It’s a sobering reminder that even the most promising technologies can be wielded with a disconcerting lack of consideration.

The fact that ByteDance continues to collect telemetry data, even after users opt-out, is deeply concerning. It suggests a fundamental misalignment between the company’s stated intentions and its actual practices.

The core issue isn’t just the loss of the LLMs; it’s the feeling that you’re being treated as a data source, not a user. It’s a weird vibe.

A Question of Endgame

I’m left wondering—what’s the endgame?

Are they simply gathering information to refine their algorithms? Or are they building a comprehensive profile of every programmer’s workflow, ready to exploit it for some future advantage? It’s a chilling thought. You start to think about the implications, right?

The silence in the IDE is still there—a constant, unsettling reminder of what’s been lost. And frankly, I’m not sure I trust ByteDance to ever give it back. It’s a frustrating situation, to say the least.