Trae: ByteDance two-form-factor coding line - TraeCode (IDE + SOLO) and TraeWork, plus a stalled MIT-open shell
trae
Trae is the AI coding line from ByteDance, and the official docs split it into two clearly different things. TraeCode is a development tool with AI deeply integrated, in two modes: IDE mode keeps the editor, terminal, debugger, extensions and source control for scenarios that need fine-grained control over code changes and execution, while SOLO mode hands the lead to AI - describe the requirement in natural language, by voice or by uploading local files, and it decomposes the task itself and runs code generation, testing, preview, change summary and deployment, with a task panel, an AI conversation panel and a tool panel (built-in editor, doc viewer, browser) from left to right. TraeWork is the AI-native workspace grown out of the SOLO mode of TraeCode, on web, desktop and mobile, in Work / Code / Design modes, aimed at product managers, data analysts, operations and designers rather than developers only. The long-task ceilings are stated concretely: Max mode extends the context window to 1M, allows up to 200 tool-call rounds per task and reads up to 750 lines per file read to cut down on chunking. bytedance/trae-agent is MIT-licensed but has not been updated for about eight months and cannot stand for the current engineering of Trae. Boundaries: no third-party benchmark readings are published (no SWE-bench or Terminal-Bench self-evidence), so every capability claim comes from feature docs and vendor descriptions; clients are closed source; 1M / 200 rounds / 750 lines are ceilings rather than typical experience and the vendor itself says they raise cost substantially; model availability is doubly limited by region (Seed, MiniMax and GLM unavailable to US users) and by plan tier, so teams across regions do not share one model set; concurrent cloud tasks are a hard tier difference and Free excludes SOLO, so evaluation cannot look at monthly price alone. Confidence C (vendor-claim).
- CONFIDENCE
- Vendor Claim
- Official model card or keynote only, no independent re-test
- KEY METRIC
- Max mode limits (context / tool rounds per task)
- Vendor Claim · 2026-09
- MATURITY
- Product
- research → demo → product → production
Editor's takeGraded C (vendor-claim). What could be verified independently is popularity and engineering fact only:
bytedance/trae-agentat 12,119 stars / 1,352 forks / MIT / last push 2026-02-05 / 191 open issues, pulled straight from the GitHub API on 2026-09-28, with the companion paper arXiv:2507.23370 checkable; and the 18-model built-in list, the 272k-tiered unit prices, and the five plans with concurrent cloud task counts (2/2/10/15/20), all published in official docs and the pricing page. But the capability claims that actually matter in this dossier - Max mode's 1M context, 200 tool rounds per task, 750 lines per read, SOLO's end-to-end delivery chain, automatic cloud failover when a device goes offline - come entirely from official product documentation, and Trae publishes no third-party benchmark readings at all (no SWE-bench or Terminal-Bench style self-evidence). None of it has been re-tested. Per contract section 13.5, "official docs only, no independent re-test" is vendor-claim; a star count is a popularity fact, not a capability reading, and cannot lift the grade to A.Water level: Trae's strategic position is a model-neutral multi-frontend dispatch layer, not an in-house-model play. Three things support that. First, its model surface is among the most heterogeneous in the market - OpenAI (GPT-6-Astra/Sol/Luna, three GPT-5.6 variants, GPT-5.5/5.4/5.2), Google (Gemini-3.1-Pro / 3-Flash), ByteDance's own Seed-2.1-Turbo, plus China's GLM-5.2, DeepSeek-V4-Flash, Kimi-K3/K2.7-Code/K2.5 and MiniMax-M3/M2.7, with BYOK on top. Trae sells orchestration and experience, not the base model. Second, it makes cross-device dispatch the product's main axis: the phone is the dispatch center, managing cloud TraeWork and several personal computers at once, assigning concurrent tasks to different devices, failing over to cloud execution automatically when a device is offline, with one account system and real-time task sync across three clients. That abstracts "which machine the agent runs on" into a schedulable resource pool, which is further along than a single-machine IDE. Third, its cost language is unusually candid - the Max mode docs state directly that enabling it significantly increases cost and that the default window is usually sufficient for everyday work. A vendor talking users out of its own high tier inside feature docs is rare in this market.
Three things worth copying: the agent workflow is explicitly decomposed into requirement analysis, code research, solution design, implementation of changes, delivery and acceptance, and the built-in Agent produces an actionable plan first and only develops step by step after you confirm it - the cheapest available gate against long-task runaway. DiffView collapses agent output into one reviewable change (affected file count, total lines changed, per-file diffs). And AI code review over uncommitted changes, a single commit or a branch diff emits summaries, flowcharts and diffs, turning review into a comprehension tool rather than a compliance step.
Risk signals stated plainly: trae-agent has had no commit in about eight months while 191 open issues keep accumulating - the open-source repo and the commercial line have diverged, so that MIT repository is not a sample of Trae's current engineering. Model availability is constrained twice over (Seed, MiniMax and GLM unavailable to US users; the whole GPT-6 and GPT-5.6 families plus GPT-5.5, GLM-5.2, DeepSeek-V4-Flash and Kimi-K3/K2.7-Code require the new plan), SOLO is excluded from Free, and only Ultra gets early access to new models. The usable model set therefore differs by region, and selecting against the public model list alone will give the wrong answer for cross-region teams.
What it is: ByteDance's two-form-factor coding line - TraeCode (IDE + SOLO) and TraeWork (web / desktop / mobile)
Trae is ByteDance's AI coding product line, and the documentation splits it into two clearly different things. TraeCode is "a development tool deeply integrated with AI capabilities", offering a complete experience across coding, project understanding, debugging and running, and change management: you can stay in control of every step as in a traditional IDE, or delegate complex tasks to agents for planning and execution. TraeWork grew out of TraeCode's SOLO mode as an AI-native workspace with web, desktop and mobile clients and three modes - Work / Code / Design - aimed beyond developers at product managers, data analysts, operations and design roles.
TraeCode's dual mode is its most recognizable structure:
- IDE mode: keeps the familiar workflows - editor, terminal, debugging, extensions, source control - for cases needing fine-grained control over code changes and execution.
- SOLO mode: AI takes the lead. Describe requirements in natural language, by voice, or by uploading local files, and the AI decomposes the task and runs the whole path: code generation, testing, preview, change summaries, deployment. The UI is task management panel, AI chat panel, tool panel (built-in editor, documentation viewer, browser).
Max mode: 1M context, 200 tool rounds per task, 750 lines per read
These are the three concrete ceilings Trae publishes for long tasks: context window expanded to a maximum of 1M, up to 200 rounds of tool invocation in a single task (for multi-step, multi-dependency work), and up to 750 lines read at a time (reducing segmented processing). Documented fits include: rapid first drafts for large complex projects (import dependencies, data structures and config files at once and produce a runnable global prototype), analysis and implementation from long documents (read a lengthy PRD, design doc or compliance agreement straight into code), cross-module and cross-file understanding and refactoring (SDK or framework upgrades, global naming conventions, cross-module API refactoring), automation scripts for complex multi-step processes (CI/CD pipelines, cross-service orchestration, automated test scripts), and context preservation during real-time interactive development.
The more interesting part is the warning Trae writes about itself: "Enabling Max mode will significantly increase costs... For everyday development tasks, the default context window is usually sufficient." A vendor talking users out of its own high tier, inside feature documentation rather than on the pricing page, is unusual honesty.
CUE and Agent: the completion layer and the execution layer are built separately
CUE is the completion-side capability set: code completion, chained completion, multi-line edits, next-edit prediction and navigation, plus dependency imports and reference renaming in Python, TypeScript and Golang projects.
Agent is the execution side. The documented five-stage workflow reads like a harness design reference: requirement analysis, code research (search the codebase, docs and online resources, locate relevant files, analyze existing implementation), solution design (break down steps and dynamically optimize the modification plan), implementation of changes (which may include recommending new dependencies, terminal commands to execute, and guidance for manual operations outside the client), and delivery and acceptance (hand control back after validation and summarize all modifications). Two agents are built in: Chat for quick technical Q&A and troubleshooting, and Agent for automated project development - its distinction from an ordinary conversational agent is that it first generates an actionable plan from your goal and project context, then develops step by step only after you confirm the plan. Custom agents are supported with configurable prompts, MCP servers and toolsets, and ready-made custom agents can be imported in one click.
The context types you can attach are also fully enumerated: files, folders, code snippets, terminal output, repositories, document sets, and even webpages.
SOLO's delivery chain: Figma to code, Supabase, Vercel, Stripe, DiffView
SOLO wires the key third parties along the design-to-production path into tools: Figma to code parses design files and converts elements into executable code, either a whole frame for a full page or precisely selected components (buttons, forms, cards); Supabase connects a cloud PostgreSQL database so you design screens and build the schema at the same time; Vercel deploys and returns a shareable link, with re-deployment as content updates; Stripe is callable as a tool for payments; and AI services can be configured and integrated into the web app as needed.
Two interaction details deserve separate mention. DiffView opens from the chat panel's Open Diff button and shows the number of affected files, total lines changed and the list of modified files, with per-file diffs - collapsing agent output into one reviewable change. Conversation Auto-Fold (Settings > Conversation > To-Do List) automatically folds and summarizes completed tasks, expandable on demand. Task management supports running multiple tasks concurrently within a single project, breaking the traditional serial model.
TraeWork: SOLO turned into a cross-device dispatch workspace
TraeWork positions itself as a "pocket AI agent hub". The three clients share one account system and task data with real-time sync, and the division of labour is explicit: mobile is the cross-device task dispatch center, while web and desktop handle task execution, deeper interaction and result review. The desktop app runs independently of TraeCode IDE, supports both local and cloud tasks, takes text, voice, attachments and skills as input, shows live progress with automatic output summaries, and lets you preview and accept results inside the chat surface. Mobile defaults to press-and-hold to speak, centrally manages cloud TraeWork plus multiple personal computers, dispatches concurrent tasks to different devices with live progress monitoring, and automatically fails over to cloud execution when a device goes offline so tasks are not interrupted.
The cloud agent provides unified runtime and dependency management, executing all code in a stable isolated remote environment and avoiding compatibility or performance issues caused by local environment differences. The three modes are aimed differently: Work for people who do not develop (documents, data, presentations), Code for engineers used to agent-driven development (coding, debugging, repository management, Git workflows), and Design for an end-to-end AI workflow of creating, refining and delivering designs.
Security and engineering furniture: Privacy mode, sandboxed execution, AI code review
With Privacy mode on, Trae does not use your chats, code snippets or AI-generated outputs for data analysis, product optimization or model training, and codebase files always remain on your local device. Sandboxed execution runs agent-generated commands in a restricted environment, reducing misuse risk through file access controls and high-risk command blocking policies.
The engineering furniture is not sacrificed to "AI first": a complete built-in Git workflow with AI-generated standardized commit messages; AI code review over uncommitted changes, individual commits or branch diffs, presented as summaries, flowcharts and diff views; an extension store for editor, language support and debugging tools; and Remote SSH / WSL for developing in remote environments.
Model surface: 18 built-in models plus BYOK, and two regional restrictions
The built-in list (each item checkable) spans three US labs and Chinese vendors: Seed-2.1-Turbo, GPT-6-Astra / Sol / Luna, GPT-5.6-Sol / Terra / Luna, GPT-5.5 / 5.4 / 5.2, GLM-5.2, DeepSeek-V4-Flash, Kimi-K3 / K2.7-Code / K2.5, Gemini-3.1-Pro-Preview / Gemini-3-Flash-Preview, MiniMax-M3 / M2.7, with custom models addable via API key. Unit prices are tiered at a 272k context boundary: GPT-6-Astra is $10 / $50 per million tokens (input / output) at or below 272k and $20 / $75 above it; GPT-6-Sol is $2 / $10, rising to $4 / $15; Seed-2.1-Turbo is $0.50 / $2.50.
Two restrictions must be stated: first, the Seed, MiniMax and GLM series are not available to users in the United States; second, GPT-6-Astra/Sol/Luna, GPT-5.6-Sol/Terra/Luna, GPT-5.5, GLM-5.2, DeepSeek-V4-Flash, Kimi-K2.7-Code and Kimi-K3 are only available after upgrading to the new plan.
Commercial terms
Five subscription tiers: Free $0, Lite $8/mo ($80/yr, about $6.70/mo), Pro $20/mo ($200/yr), Pro+ $60/mo ($600/yr), Ultra $200/mo ($2,000/yr, about $166.70/mo), plus On-Demand Usage. Concurrent cloud tasks scale by tier: 2 / 2 / 10 / 15 / 20; SOLO mode is not included in Free; only Ultra gets early access to new models. Lite is regional pricing, offered only in Thailand, Indonesia, Vietnam, the Philippines, India, Pakistan, Turkey, Malaysia, Brazil, Colombia, Peru and Nigeria.
trae-agent: the open-source half, and its stall signal
Trae has an MIT-licensed open-source command-line agent, bytedance/trae-agent, from ByteDance's Lakeview research team with an accompanying paper, arXiv:2507.23370. It supports multiple LLM providers, records full execution trajectories for replay and training, and is configured in YAML (max_steps defaults to 200). GitHub data as of 2026-09-28: 12,119 stars, 1,352 forks, 191 open issues, not archived. To be plain about it: the last push was 2026-02-05, roughly eight months without a commit while 191 open issues keep accumulating - the open-source repository and the commercial product line have clearly diverged in iteration pace.
Boundaries
Trae publishes no third-party benchmark readings (no SWE-bench or Terminal-Bench style self-evidence); every capability claim comes from feature documentation and vendor description. The clients are closed source, and while trae-agent is MIT-licensed it has not been updated in about eight months, so it cannot represent Trae's current engineering implementation. Max mode's 1M / 200 rounds / 750 lines are ceilings, not typical experience, and the vendor itself says costs rise significantly. Model availability is constrained twice over - by region (Seed, MiniMax and GLM unavailable to US users) and by plan tier - so the usable model set differs across teams in different regions. Concurrent cloud tasks are a hard tier differentiator and SOLO is excluded from Free, so evaluation cannot look at monthly price alone.