Aider vs Trae (2026)

Tool surface is deliberately narrow: git, linters, test runners, a web scraper and voice. No MCP client and no general tool calling framework, which is a real gap against the rest of this lane.

Upgraded from P: architect mode is a documented two model plan then edit pipeline with its own edit formats, plus an auto lint and auto test loop where the agent fixes what it breaks. That is multi step execution, not a single request response.

Upgraded from N: watch mode, in-code AI comments, a scriptable one shot message flag, a browser UI and voice input are five distinct invocation paths. Held at P because there is no scheduling, event or repository trigger surface.

Upgraded from P: this is a genuine retrieval architecture over the customer's own codebase, graph ranked and dynamically budgeted, not a context window stuffed with files. Distinctive enough that it is the vendor's headline capability.

Upgraded from P: git is the persistence layer here, deliberately. Every edit is a commit with a generated message, so history, diff and revert are durable and inspectable across sessions using tools the team already has.

Local only single developer tool with no hosted service, no accounts and no organisation layer, so there is no identity or governance surface to grade and none is claimed. N here reflects a design choice, not a gap the vendor is hiding; the privacy posture is genuinely strong but posture alone does not clear the P floor.

SET TO U ON MIKE'S RULING OF 2026-08-30, under the new standing rule that where a cell's only support is a source the conventions exclude and no first-party evidence can be reached, the grade goes to U rather than None. This is not a cell we failed to verify; it is a cell whose basis was invalid. The prior grade was None, sourced to morphllm.com/comparisons/trae-vs-cursor, a COMPETITOR COMPARISON PAGE. Section 7 states such pages can confirm a capability exists but never that one is absent or limited, so the source could not support the grade it was given. First-party evidence also contradicts the premise: trae.ai/pricing carries an enterprise route reading 'Looking for enterprise solutions? Contact us via BytePlus', so an enterprise offering does exist even though its contents were unreachable. No first-party material on security was reachable on either pass. trae.ai/pricing renders client-side and returned only headings and footer links; www.byteplus.com/product/trae is a React shell returning a JavaScript notice; docs.trae.ai is ROBOTS-DISALLOWED. Score is unchanged at 0.0 so nothing downstream moves; the difference is that Unspecified admits we do not know rather than asserting absence. Anchors for a dedicated pass: search snippets of specific docs pages rather than fetches, plus trae.ai/terms-of-service and trae.ai/privacy-policy, which may render server-side.

Upgraded from P: git as an audit trail is unusually strong for a local agent. Every action is a durable, attributable, revertible commit inspectable with standard tooling, which is closer to reconstructing what happened than most vendors in this lane manage.

SET TO U ON MIKE'S RULING OF 2026-08-30, under the new standing rule that where a cell's only support is a source the conventions exclude and no first-party evidence can be reached, the grade goes to U rather than None. The prior grade was None, sourced to morphllm.com/comparisons/trae-vs-cursor, a COMPETITOR COMPARISON PAGE asserting that no self-hosted or on-premises option exists. Section 7 states such pages can confirm a capability exists but never that one is absent or limited, so the source could not support the grade. Unlike the Security cell there is no first-party evidence pointing the other way, but there is none pointing this way either, and a None here asserts an absence nobody established. No first-party material on deployment was reachable: the pricing page renders client-side, the BytePlus enterprise page returns a JavaScript notice, and docs.trae.ai is robots-disallowed. Score unchanged at 0.0. Worth noting for a dedicated pass that vendor-authored copy syndicated to a directory describes local-first codebase storage with temporary index uploads deleted after processing, and data deployed by account location across the United States, Singapore and Malaysia; if confirmed first-party that is a genuine residency property and this cell would move to P.

Scriptability plus an Apache 2.0 codebase is real extensibility, but there is no published API reference, no SDK and no MCP server, which is the gap against most of this lane.

Upgraded from P per the axis rule: auto lint and auto test with the agent fixing what it broke is a customer facing loop that tests the agent's own output, and the polyglot leaderboard is a published evaluation harness the vendor maintains for exactly this purpose.

The web scraper fetches pages as context via httpx or playwright, which is retrieval rather than the agent operating software through a UI; the axis test is not met.