Skip to guide

Use onemind with TRAE

TRAE has a Project instruction adapter, but its MCP connection remains manual/unverified. TRAE has no managed skills via onemind, but a shared ~/.agents/skills/onemind skill can be installed separately. Native BETA sync also maintains a stable user-wide bootstrap in ~/Library/Application Support/Trae/User/settings/user_rules.md; Project content stays in the bound folder.

macOS app

In the app, connect TRAE from Team and bind the Project folder before Mind Sync.

  1. Sign in to OneMind BETA.app and connect TRAE from Team.
  2. Open Mind, choose the intended Project, and bind its exact folder on this Mac.
  3. Open the approved Mind, choose Sync, check the tool/device, and choose Sync now. Wait for confirmed delivery.
  4. Start a new TRAE session from that folder. See Mind Sync for pending, offline, and recovery states.

CLI

From the repository you open in TRAE, run:

onemind project trae .

The CLI detects TRAE and prints a message asking you to open onemind and choose the Project Mind for the detected folder. Open the onemind app, find the detected folder in Sync Setup, and bind it to the intended Project Mind. Then run:

onemind sync
onemind status

Confirm that <repository>/AGENTS.md contains an onemind-managed block, then reopen TRAE or start a new TRAE session. On the first write, onemind saves the previous file at <repository>/.one-mind/AGENTS.md.backup.

Running onemind trae [PATH] calls the same detection step as onemind project trae, adding an inactive target. New native folder bindings are scoped to the exact Project, tool, and device; do not use the legacy shorthand to move an existing native binding.

To add MCP capabilities, import https://onemind.team/mcp in the TRAE project's MCP settings and approve OAuth there. Because this connection is managed through TRAE's UI and has no verifiable local inventory, onemind reports only Package prepared, not Host connected.

Use onemind integrations install trae to prepare the shared skill package at ~/.agents/skills/onemind. onemind never invents a ~/.trae plugin directory.

For an activated TRAE Project binding, onemind can sync reviewed memory and, when upload is enabled for the target in Sync Setup, upload that Project's structured onemind proposal queue. It never reads TRAE's proprietary chat database or treats arbitrary file changes as durable knowledge.