feat(trae): add ZERO-294 Trae adapter

[spencercharest]

Summary

Subtask: ZERO-310

Adds a Trae adapter for Zero without touching guides/agent-install.md:

• project skill at .trae/skills/zero/SKILL.md
• optional Agent Skills copy at .agents/skills/zero/SKILL.md
• project MCP config at .trae/mcp.json
• Trae MCP import link artifact for https://mcp.zero.xyz
• always-on project rule at .trae/rules/zero.md
• /zero project command at .trae/commands/zero.md
• scripts/build-trae.sh packaging into dist/zero-trae/
• standalone consumer guide at guides/trae.md and README install link
• version bump to 1.4.0 via make minor

Official Sources Used

• Trae skills: https://docs.trae.ai/ide/skills
• Trae MCP overview: https://docs.trae.ai/ide/model-context-protocol
• Add MCP servers / project .trae/mcp.json: https://docs.trae.ai/ide/add-mcp-servers
• MCP install links: https://docs.trae.ai/ide/mcp-server-install-links
• MCP in agents: https://docs.trae.ai/ide/use-mcp-servers-in-agents
• Trae rules: https://docs.trae.ai/ide/rules
• Trae slash commands: https://docs.trae.ai/ide/slash-commands

Human Install / Update Flow

Inside Trae:

1. Run the standalone Zero installer once:

   curl -fsSL https://zero.xyz/install.sh | bash

2. Build and copy the adapter into the Trae project:

   scripts/build-trae.sh
   cp -R dist/zero-trae/. /path/to/your/project/

3. Open the project in Trae.
4. In Settings > Skills & Commands, confirm the zero project skill is enabled.
5. In Settings > MCP, enable project-level MCP and confirm the Zero server from .trae/mcp.json.
6. Use /zero or ask Trae to help set up and test Zero.

Alternative MCP UI path: open the link in dist/zero-trae/trae/mcp-install-link.txt and confirm the imported Zero MCP server in Trae.

Updates are manual because Trae has no documented lifecycle hooks for this adapter:

curl -fsSL https://zero.xyz/install.sh | bash
scripts/build-trae.sh
cp -R dist/zero-trae/. /path/to/your/project/

Proposed guides/agent-install.md Notes

Do not merge these into guides/agent-install.md from this PR. Capture them during the later runbook rework:

• Trae reads default project skills from .trae/skills/{skill_name}/SKILL.md.
• Trae can also read .agents/skills/, but only when Settings > Skills & Commands enables the .agents directory toggle.
• If both .trae/skills/zero and .agents/skills/zero exist, Trae prioritizes .trae/skills/zero.
• Project MCP servers can be declared in .trae/mcp.json once Settings > MCP enables project-level MCP.
• The Zero MCP config for Trae is:

  {
    "mcpServers": {
      "zero": {
        "url": "https://mcp.zero.xyz"
      }
    }
  }

• Trae also supports trae://trae.ai-ide/mcp-import?type=http&name=zero&config=... install links; this adapter ships the generated link in trae/mcp-install-link.txt.
• Trae project rules live in .trae/rules/; use alwaysApply: true for the Zero context reminder.
• Trae project commands live in .trae/commands/; this adapter ships /zero as .trae/commands/zero.md.
• Trae has no documented SessionStart, UserPromptSubmit, or PreToolUse hooks. Do not document automatic runner provisioning, automatic adapter updates, or programmable command approval for Trae.
• Runner install/update remains the standalone flow: curl -fsSL https://zero.xyz/install.sh | bash.

Verification

Local validation:

make minor
scripts/build-trae.sh --tar dist/zero-trae.tgz
jq . plugins/zero-trae/manifest.json plugins/zero-trae/trae/mcp.json
make version
cmp -s plugins/zero/skills/zero/SKILL.md dist/zero-trae/.trae/skills/zero/SKILL.md
cmp -s plugins/zero/skills/zero/SKILL.md dist/zero-trae/.agents/skills/zero/SKILL.md
git diff --check
git diff -- guides/agent-install.md

Docker validation used copied host auth from ~/.zero:

docker run --rm \
  -v "$PWD":/workspace \
  -v "$HOME/.zero":/host-zero:ro \
  -v "$HOME/zeroclick/env":/tmp/host-env:ro \
  node:22-bookworm bash -lc 'cp -R /host-zero "$HOME/.zero" && npm install -g @zeroxyz/cli@latest && cd /workspace && scripts/build-trae.sh --tar dist/zero-trae-docker.tgz && zero auth whoami --json && zero search "cdn.withzero.xyz upload txt file" --json && zero get cdn-withzero-xyz-static-site-file-cdn-upload-a0d9f22f && zero fetch --json --capability cdn-withzero-xyz-static-site-file-cdn-upload-a0d9f22f https://cdn.withzero.xyz/api/v1/uploads -d @/tmp/zero-cdn-body.json --max-pay 0.001'

Zero E2E result:

• ~/.zero copied into Docker: yes
• run ID: run__1po4i54yMSfY_kPJg-wC
• returned URL: https://cdn.withzero.xyz/LolkTqxW/agent-harness-e2e-trae-docker-20260615T003857Z.txt
• verified body: ZERO-310 Trae Docker copied-auth CDN upload check 20260615T003857Z
• payment: 0 USDC via mpp on tempo
• zero review: intentionally not run

Claude-style plugin compatibility and simpler install option

Full Claude Code plugin package support: No. Trae has Trae-specific skills, rules, commands, and MCP config. It can optionally read .agents/skills, but it does not install Claude Code .claude-plugin packages.

What this means for users:

• Build scripts should be maintainer/release packaging only.

• Consumer-friendly flow should use Trae's native skill import and MCP import/UI surfaces:

  1. Import/install the prebuilt Zero skill package in Trae.
  2. Add Zero MCP with Trae's MCP import link or project MCP setting for https://mcp.zero.xyz.
  3. Use the included Trae command/rule files only if installing the full prebuilt artifact.
  

• If the Trae-specific adapter is too much maintenance, ship skill + MCP import instructions only. There is no Claude plugin shortcut.

GitHub Releases / no-build install check

Result: No confirmed Gemini-style GitHub Release install path. Trae has native skills, commands, rules, MCP import/settings, and a plugin area, but I did not verify an official Trae flow that installs this kind of adapter directly from GitHub Release assets.

Best no-build consumer path should use Trae-native import/UI surfaces:

1. Import/install the prebuilt Zero skill package in Trae.
2. Add Zero MCP with Trae's MCP import link or project MCP setting for https://mcp.zero.xyz.
3. Use a prebuilt artifact only for optional rules/commands.

A GitHub Release asset can avoid local builds by publishing ready-to-copy zero-trae files, but unless Trae documents release-asset installation it should be framed as manual download/extract, not a Gemini-style installer.

PR State

Draft. The package, file layout, Trae config JSON, MCP install link, copied-auth Zero loop, and CDN upload were verified in Docker. Full in-product verification still needs a human Trae Desktop / Trae IDE session because Trae has no documented local headless Agent CLI or plugin loader command for this adapter surface.

[spencercharest]

Folded into #63 as a matrix entry (trae in plugins/zero/agents.json) — a minimal standalone entry: global skills at ~/.trae/skills (community-verified path; #63 flags one in-product check). No hooks (Trae has none) and no user-level MCP JSON file to carry. The adapter-template work here stays available on this branch if we later ship per-host templates.