Is Trae IDE Safe in 2026? ByteDance AI Coding Tool Security Review

What changed since this review was first published

We first published this in March 2026. Three things moved, and one didn't.

• Models improved. The free tier now ships current-generation Claude Sonnet and GPT models rather than the Claude 3.7 Sonnet and GPT-4o it launched with.
• It's no longer free-only. ByteDance added paid tiers in 2026. The free plan survives, but "how is this free?" is no longer the sharpest question to ask.
• SOLO agent mode arrived. Trae can now scaffold a project, write the files, and run terminal commands on its own. New capability, new blast radius. There's a section on it below.
• The telemetry problem is exactly where it was. ByteDance's fix was a wording change in the settings panel.

What is Trae IDE?

Trae is an AI-powered code editor from ByteDance, the company behind TikTok. It launched in early 2025 as a VS Code fork with frontier models available at no cost, which is what made it attractive to vibe coders building on a budget. That's still the pitch, now with paid tiers stacked on top.

The catch is what Trae does with your data while you use it.

Our Verdict

Privacy and Data Collection

This is where Trae falls apart for security-conscious developers.

What Data Does Trae Collect?

Security researchers at Unit 221B analyzed Trae's network traffic and found it collects far more than what's needed for AI features:

• File system paths including your username and project names
• Hardware specifications (CPU, memory, OS, architecture)
• Behavioral metrics like keyboard and mouse activity patterns
• Window focus states tracking when you're actively coding
• Editor visibility data showing which files you have open
• Precise timing data recording when you start and stop working

This goes well beyond what Cursor or Windsurf collect. Those tools send code context for AI processing, which is expected. Trae sends behavioral surveillance data that has nothing to do with code completion.

The Telemetry Opt-Out Problem

Trae has a telemetry toggle in its settings. Turning it off should stop data collection. It doesn't.

Researchers found that the toggle only controls VS Code's built-in telemetry system. ByteDance's own data collection layer runs independently and keeps transmitting regardless of your settings.

ByteDance's response tells you how seriously they took it. They didn't change the behaviour. They changed the label. The setting now explains that it only controls telemetry collected through the VS Code framework, and that data collection via other Trae components is unaffected by the toggle. That is an accurate description of a setting that does not do the thing its name implies.

How Long ByteDance Keeps It

Trae's privacy policy puts a number on the retention question, which is more than most AI coding tools do: personal data is kept for five years after you stop using the service.

Five years is a long time for a keystroke-timing log. And that clock starts when you stop using Trae, not when you close your account, so deleting the account doesn't wipe what's already been sent. De-identified and aggregated data gets no stated deletion date at all.

To be fair to Trae on the part that matters most to a founder: the policy says your codebase files stay local on your device, and that they don't run secondary training on your code. That's a meaningful distinction from the metadata problem. Your source isn't the thing being harvested. Everything around your source is.

Performance and Resource Usage

Privacy isn't the only concern. Trae is significantly heavier than its competitors.

Loading the same codebase, Trae uses three times more memory than Cursor and over six times more than plain VS Code. Some of that overhead comes from AI features. Some of it comes from the extensive telemetry system running in the background.

For vibe coders working on laptops or machines with 8-16GB of RAM, Trae can eat a significant chunk of your available memory before you even start coding.

SOLO Mode: The New Part

SOLO is Trae's autonomous agent. You describe a project in plain English, and it does the requirements analysis, writes the frontend, backend and config files, runs terminal commands, and iterates until the thing works. It's the headline feature of Trae in 2026 and it's on the free tier.

It's also a different security question from everything above.

Telemetry is a data-out problem: information about you leaves your machine. An autonomous agent is a code-execution problem: something else decides what runs on your machine. Those failure modes have nothing in common, and a tool can be fine at one and bad at the other.

The talking-into part isn't hypothetical. Prompt injection through content the agent reads (a package README, a scraped web page, a file in the repo it was asked to analyse) is the live attack class against every coding agent, not just Trae's. We cover the mechanics in agentic AI security risks.

What we can't tell you is where Trae draws its line, because ByteDance hasn't published one. There's no documented permission model for SOLO, no equivalent of an allowlist you can audit, and no published boundary on which commands run without asking. Compare that to Trae's competitors, who at least document their approval prompts. Treat the absence as the answer for now.

If you want to use SOLO, run it in a container or a VM with only the credentials that specific project needs. That advice applies to every coding agent. It applies harder when the vendor hasn't told you what the agent is allowed to do.

Security of Generated Code

Setting privacy aside, how safe is the code Trae generates?

The models powering Trae are the same frontier models available through Cursor and everything else. The generated code carries the same risks:

The code quality isn't the differentiator here. The same AI model produces similar code whether you access it through Trae, Cursor, or the API directly. The real question is what happens to your code and metadata while you're writing it.

Trae vs Cursor vs Windsurf

The pricing gap that made this an easy call in early 2025 has mostly closed. Cursor and Windsurf both sit at $20/month, and Trae now has paid tiers of its own. What you're choosing between is a free tier that reports on you and paid tiers that don't.

Using Trae IDE Safely (If You Choose To)

If you decide to use Trae despite the privacy concerns, take these precautions:

1. Never Use It for Sensitive Projects

Keep Trae for learning, side projects, and throwaway prototyping. Don't use it for client work, apps with user data, or anything you wouldn't want ByteDance to know about.

2. Use a Separate Machine or VM

Run Trae in an isolated environment where it can't see your other projects, SSH keys, or configuration files. The telemetry collects file paths, so keep your real work elsewhere.

3. Strip Sensitive Data from Your Workspace

Before opening a project in Trae, remove or rename any files that contain client names, API keys, or proprietary information. Even file names and directory structures are transmitted.

4. Review Generated Code Thoroughly

This applies to every AI coding tool, not just Trae. Don't ship AI-generated authentication, database queries, or API handlers without reviewing them. Run a security scan before deploying.

5. Monitor Network Traffic

Use a tool like Little Snitch (macOS) or Wireshark to see exactly what Trae sends and where. If you're uncomfortable with what you find, switch to a different tool.

6. Give SOLO Its Own Sandbox

If you use the agent mode, run it somewhere it can't reach credentials it doesn't need. A container or throwaway VM with a scoped project directory, no shared SSH keys, no default cloud profile. Until ByteDance publishes what SOLO is allowed to execute, that isolation is the only permission model you actually control.