Use ShardStitch with Trae.

This Trae profile uses the project rules path documented for Trae v1.3.0 and later, plus a manually added MCP server when desired. Confirm the current version and path migration before relying on old rule files.

After-death behavior: Partial. Disk recovery plus local recovery capture where available; handoff-in uses the rules folder.

Integration paths.

Hand-off in

.trae/rules/project_rules.md for Trae v1.3.0+; old paths are auto-migrated.

MCP

Manual. Settings -> MCP -> Add, or a .mcp.json stdio block.

Session recovery

Project rules seed context; confirm active version and workspace before resuming.

Setup path.

Run ShardStitch inside the project.

Generate project_rules.md, open the intended workspace, and check that the current Trae version reads the migrated path. Add MCP through Settings or a project server block only if live calls are needed.

Write the Trae handoff.

Write project_rules.md and add MCP manually if you want live tool calls.

Start clean.

Ask Trae to confirm the project root and summarize the handoff goal before it starts another edit or retry.

Limits to know.

Rule-file behavior can differ across versions, and an old path may have been migrated. MCP is manual here; neither integration recreates the old Trae conversation or proves a tool call completed.

Best use case.

Keeping Trae from retrying failed branches after a reset.

FAQ.

Is an old Trae rule path still the active pickup file?

This page names the v1.3.0+ path and notes migration behavior. Check the installed version and the project rules Trae actually loads before continuing.

Get ShardStitch

Resume this workflow.

For a task trapped in retries, stop the loop, preserve the diff and last output, then restart with the project rule file visible. Have Trae propose one bounded check and inspect its result before allowing another edit cycle.

Confirm Trae can access the project rule file in the selected workspace, then compare its proposed next check against the preserved diff.

Primary source and delivery boundary.

TRAE issue 1118 (checked September 27, 2026). A June 17, 2025 report describes an Analyzing state that persists on macOS. It is related symptom evidence, not proof of a Windows process crash or a universal fix. The issue is closed without a verified fix release established here.

Tool-specific troubleshooting

For symptom-specific diagnostics and recovery steps, use the focused guide: Troubleshoot Trae.