EN
Back to the archive

The archive · Developer & Business Tools · Product decision · 2025

Trae: ByteDance's AI IDE telemetry expose draws 954-point HN backlash

ByteDance's free AI-native VSCode fork Trae streams telemetry past opt-out; a July 2025 expose drew 954 HN points and a promised privacy mode.

Trae (ByteDance)

The betDevelopers would accept a free AI-native IDE whose usage data streams to ByteDance, even when telemetry is presented as optional and switched off.Live

What the business is

Trae is ByteDance's free AI coding IDE — a customized fork of Visual Studio Code that bundles AI assistance and streams usage telemetry to ByteDance infrastructure.

How it started

Trae is ByteDance's customized fork of Visual Studio Code, given away as an AI-powered IDE. When a researcher began probing it on 2025-07-24 and shared findings in Trae's official Discord, messages were auto-flagged by a keyword blacklist that matched the word 'tokens' — initially read as censorship, later explained by the team as a misconfigured moderation system.

What happened

A follow-up investigation on 2025-07-31 focused on network traffic. Even with telemetry settings switched off, Trae kept persistent connections to ByteDance endpoints (mon-va.byteoversea.com and maliva-mcs.byteoversea.com); roughly seven minutes of normal use produced more than 500 calls totaling about 26 MB, with single batches exceeding 53 KB. Payloads carried hardware identifiers, OS and locale data, workspace IDs, editor-language activity, and focus timing. ByteDance's team responded by reaching out to the researcher, adding in-product telemetry acknowledgements, and saying a dedicated Privacy Mode was scheduled for release around August 2025.

No ending yet — it is still running.

Background

ByteDance's Trae is a customized fork of Visual Studio Code, given away as a free AI-native IDE — the same distribution wedge ByteDance has used across products, bundling frontier AI into a familiar developer surface. A researcher's July 2025 investigation found the trade-off buried in the plumbing: Trae kept persistent connections to ByteDance endpoints even after telemetry was switched off.

The report measured more than 500 calls and roughly 26 MB of traffic in seven minutes of ordinary use, with payloads carrying hardware identifiers, OS and locale details, workspace IDs, and per-activity timing. It also documented that sharing the findings in Trae's official Discord triggered automatic flagging on the keyword 'tokens', which the team later called a misconfigured moderation system rather than censorship.

By the follow-up on 2025-07-31, Trae's team had reached out, added in-product telemetry acknowledgements, and said a Privacy Mode was scheduled near August 2025. The episode put the product question on HN's front page: whether a free AI IDE from a data-driven parent can credibly offer privacy by default.

What has to be true

  • Trae copied the familiar VSCode surface and gave away frontier AI models free, betting distribution could outrun privacy concerns
  • Telemetry was framed as optional in the settings UI while connections and payloads continued, turning a configuration bug into a trust problem
  • The Discord auto-flag made ByteDance look like it was silencing criticism, amplifying the story before the keyword filter was explained
  • Publishing reproducible packet evidence on GitHub gave HN reviewers something to verify instead of a vendor denial to argue with

What can be applied

In developer tools, an opt-out that still transmits data becomes a lie: one reproducible packet capture on HN outweighs any marketing, so privacy defaults must be the product, not a promise.

Aftermath

As of 2025-07-31, Trae remains live and ByteDance's team is responding: it contacted the researcher, clarified that the Discord moderation flag came from a keyword-matching misconfiguration, and added telemetry disclosures inside the IDE UI. A dedicated Privacy Mode was said to be scheduled for release around August 2025; the research repo documents the traffic and invites reproduction, and no independent confirmation that opt-out fully stopped data flow was available in the source material.

Sources

spotted an error? The archive wants to know.

Your turn

You just read one. Describe what you are building, and see who is betting on the same thing.

Free account · 3 free questions · no card

Related cases