Skip to main content
World Wide TechnologyBenchAI tool benchmarks
Coding Assistant
StatusWatch
SignalTracked
EvidenceGrade B

Trae AI

43
D -5 vs last quarter

ByteDance VS Code fork.

UX / DXCapabilityReliabilityValueCommunityEnterpriseAutonomyIntegration

Dimension breakdown

Score · confidence
UX / DX
50% conf50
Capability
50% conf50
ReliabilityIncomplete data at this time
Value
50% conf45
CommunityIncomplete data at this time
Enterprise / Compliance
50% conf20
Autonomy
50% conf50
Integration
50% conf40
Sources blend review platforms, community sentiment, the Signal Radar and practitioner ratings. Scores re-blend each quarter.

ByteDance VS Code fork. SOLO Mode GA + SOLO Mobile (iOS/Android) for cross-device handoff, Plan Mode, multi-task parallelism, Sub Agent, DiffView, CodeGraph.

MCP marketplace 11K+ protocols; Trae Agent open-source at 11.6K stars (SWE-bench Verified 71% / #1 with Claude 4). Free + Lite $3/mo + Pro $10/mo token-based tiers (Feb 2026).

Caution

Trustpilot ~2-star persists (unsolicited code changes, March 2026 pre-trial billing charges, support ghosting); independent reviews flag linter blindness, context loss on long sessions, large-project slowdown.

Critical

telemetry concern unresolved — Privacy Mode now documented for IDE+SOLO but unverified by independent researchers, third-party extension telemetry out of scope, ToS still claims training rights.

No SOC 2, no SSO/SAML/SCIM, no enterprise tier, no admin console. ByteDance ownership + FAR 52.204-27 federal-contractor prohibition keep Trae out of US federal/regulated workloads.

Not enterprise viable.

Recommended

Use cases

Not yet assessed — this section fills in as ACES research covers the tool.

Score caps

Risk flags

  • No enterprise features

    enterpriseConditional

    No enterprise customers/features

    Caps all dimensions at 70

    Removed whenEnterprise tier launched with SSO, audit logs, or compliance certification

  • Severe negative sentiment

    trustTemporary

    Widespread negative sentiment (sentiment score 1-2)

    Removed whenSustained sentiment improvement over 90+ days with community acknowledgment of fixes

Assessment

Status rationale

Not Enterprise Viable. Strong technical capabilities (SOLO Mode + Mobile cross-device handoff, CodeGraph, SWE-bench 71%, MCP marketplace 11K+, parallel agents) but zero enterprise governance foundation.

No SOC 2, no SSO/SAML, no enterprise tier, no admin console. Telemetry controversy persists — Privacy Mode documented for IDE+SOLO but unverified by independent researchers, third-party extension telemetry remains out of scope, ToS still asserts training rights.

ByteDance ownership + FAR 52.204-27 federal contractor prohibition create structural compliance barriers beyond technical remediation. Mixed-to-negative user sentiment (Trustpilot ~2-star, March 2026 pre-trial billing charges, support ghosting, reliability complaints).

Token-based pricing introduces budget unpredictability. Not recommended for enterprise use.

Watch for

Movement triggers

Upgrade if: (1) Independent verification Privacy Mode achieves zero telemetry post-opt-out, (2) SOC 2 certification, (3) SSO/SAML/SCIM and admin console, (4) ToS amendment removing training rights, (5) Enterprise tier with dedicated support and SLAs, (6) Named Fortune 500 customer disclosed publicly, (7) Trustpilot rating recovery above 3.5 stars sustained. ByteDance ownership + FAR 52.204-27 likely prevent US federal/defense and many Fortune 500 adoptions regardless of technical improvements.

Downgrade if: pricing becomes fully opaque, security vulnerability discovered, additional ByteDance legislation restricts US enterprise access, SOLO Mobile generates a new privacy incident, or reliability complaints escalate to a documented community exodus.

Caution

Risks & limitations

  • No Enterprise Features

    Moderate

    Radar cap: no-enterprise-features

  • Severe Negative Sentiment

    Moderate

    Radar cap: severe-negative-sentiment

Capabilities

Integration surface

Not yet assessed — this section fills in as ACES research covers the tool.

Proof points

Adoption & benchmarks

Not yet assessed — this section fills in as ACES research covers the tool.

Spotted something wrong or missing here? Suggest a change →

Per-source contributions

Click any dimension to see the underlying sources and citations.