Trae is ByteDance's entry into the AI IDE market and it competes primarily on price, which it does successfully. The tiers run Free, Lite at around $3 a month, Pro at around $10, Pro+ at around $30 and Ultra at around $100, against a market where Cursor's standard plan sits at $20 and most serious alternatives are similar. For a student, a hobbyist or somebody in a market where twenty dollars a month is a meaningful sum, that gap is not trivial and it deserves to be stated plainly rather than sneered at. SOLO mode is the flagship feature, an autonomous agent that scaffolds whole projects from a plain English description, shipped as a standalone application in March 2026 and included on every paid plan with limited access on Free.
Including it rather than charging separately is the right decision commercially and the documentation on how to use it is serviceable. The billing change is the first thing a prospective user should understand. In early 2026 Trae moved from a fixed-request model to a token-based usage model, converting AI work into a dollar-denominated usage balance deducted from a monthly allocation. That is a materially different product from the one people signed up for.
Under a request model you know what a month buys. Under a token model you find out afterwards, and the heavier your usage the less predictable it becomes. The documentation explains the mechanics adequately once you find them, but the shift is exactly the sort of thing that should be prominent and is not. The documentation itself is the weakest part of the offering.
It covers the editor, the agent workflows and the configuration surface, and it is accurate as far as I could verify, but the quality is uneven and reads as translated in places, with occasional passages where the meaning has to be reconstructed from context. Compared to the documentation Cursor and Zed maintain, it is a step down. The other structural annoyance is that model access shifts between tiers over time, so what a given plan actually gives you is a moving target and the docs are not always the first thing updated when it moves. Now the part that most reviews skip.
Trae is a ByteDance product, and ByteDance is subject to a set of regulatory and geopolitical questions that a code editor makes newly concrete, because a code editor sees your entire codebase. Whatever your view of those questions, the practical position is that many organisations have policies restricting ByteDance software on work machines, and an individual developer installing this on a laptop with client code on it may be violating an agreement they have not read recently. The documentation does not raise this, which is unsurprising and still unhelpful. I am not telling anybody it is unsafe, because I have not audited it and neither has anyone else publicly.
I am saying the question exists and that you should answer it deliberately rather than by default. For personal projects, learning, or open-source work, the calculus is easy and the price is genuinely attractive. For proprietary work at an employer, check first. Two point nine.
Real capability at a price nobody else is matching, with documentation that is adequate rather than good, a billing model that changed under its users, and an ownership question the material never acknowledges.