Trae

Host entry

A desktop app or standalone editor owns window state, sign-in, project indexing, embedded terminal behavior, and local product storage.

Host owns

The desktop host owns orchestration UI, model routing, approval UX, background jobs, and any cloud or app-store managed extension points.

Connector role

agent-connector can write documented workspace/global config and content files, but it does not replace the desktop runtime or UI shell. Current wired connector surfaces: MCP server, Skills, Memory.

Implementation consequence

Desktop surfaces need source-review separation because product pages often document capabilities while runtime state lives in app-managed storage. Visible host-native gaps for this surface: Subagents.

Source pass

Current source review findings are kept as the first architecture section so readers can separate external evidence from the generated local coverage model.

• The public repository is explicitly the official GitHub for TRAE, but it is a thin tracker rather than a full source tree for the product runtime.
• TRAE should therefore be documented as a product/IDE host with source-light evidence, not as a fully inspectable open-source implementation.
• The adapter can describe MCP-only coverage and known product source links, while avoiding unverified claims about file-authored hooks or subagents.

Runtime boundary

The archive should treat Trae as a split evidence host: the open-source Trae Agent is a software-engineering agent project, while Trae AI is an IDE product. The adapter row must name which runtime it can install into.

• The open repository frames Trae Agent as a general-purpose software-engineering agent.
• The paper describes ensemble reasoning for repository-level issue resolution.
• The website is product-facing and does not by itself reveal every local storage contract.

MCP registration

Trae should be represented as MCP-capable only where the local adapter or public source gives a concrete server registration shape. Product-level integration language should not be converted into an MCP file contract without evidence.

• Open-source agent evidence can guide CLI architecture review.
• IDE product evidence should remain source-light until exact extension or settings paths are verified.

Hook bridge

The current connector matrix classifies Trae as MCP-only. That means architecture notes should avoid claiming lifecycle hooks even if the agent research system has modular stages, pruning, generation, or selection agents.

• Research-agent modules are not automatically installable hook events.
• Future hook support should identify a concrete local API or file-based bridge.

Content surfaces

Trae's useful study surfaces are repository understanding, issue resolution, multi-stage agent reasoning, IDE product UX, and model/provider integration. These are content and orchestration concepts, not necessarily connector-owned command files.

• The paper's generator, pruning, and selection roles are architecture evidence for multi-agent reasoning.
• IDE rules, prompts, or workspace state need separate source review before page chips are upgraded.

Marketplace and host-only affordances

Trae's host-only affordance is the combination of an agentic IDE product and an open research agent lineage. The page should show that duality so students can compare productized IDE agents with research/runtime agents.

• The open-source row is useful for algorithmic architecture study.
• The proprietary IDE row should remain cautious about storage, hooks, and marketplace claims.

Host-specific shape

Trae is a desktop IDE host with MCP, skills, and memory wired; custom agents are host-native but UI/cloud-share driven, so they remain a visible file-surface gap.

• Form factor: Desktop.
• Native surfaces: MCP server, Skills, Subagents, Memory.
• Wired surfaces: MCP server, Skills, Memory.
• Visible gaps: Subagents.

Hooks

No user-installable lifecycle hook boundary is confirmed for this host.

MCP

The adapter writes this host's native MCP registration dialect, including its root key, scope, transport fields, and environment syntax.

Memory

Managed memory text is written into the rules or memory file this host actually reads, with ownership markers for reversible uninstall.

Marketplace and affordances

Current install is a direct native-file write path; any package artifact is manual unless a driver is added.

• Runtime handlers: none.
• User-visible affordances: Users see managed skills + memory surfaces after install; runtime-only surfaces stay behind the host boundary..