> ## Documentation Index
> Fetch the complete documentation index at: https://renor.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Trae

> Give Trae durable memory with Renor, so a new chat starts with what the last one decided.

Trae tells you when a chat has grown too long and suggests starting a new one. A new chat starts empty. With Renor connected, Trae saves what was decided before you leave and reads it back at the start of the next chat, so you do not repeat yourself.

## Connect without an account

Add this in Trae under Settings, MCP, Add Manually (or save it as `.trae/mcp.json` in a project). It keeps your notes in a folder on your machine and needs Node 22.16 or later.

```json theme={null}
{
  "mcpServers": {
    "renor": {
      "command": "npx",
      "args": ["-y", "renor-engine", "mcp"],
      "env": { "RENOR_MCP_TOOLS": "coding" }
    }
  }
}
```

## Connect the hosted server

Create a connection key in the Renor dashboard under API keys, then use this block, replacing `YOUR_RENOR_TOKEN` in Trae's settings editor and never in chat:

```json theme={null}
{
  "mcpServers": {
    "renor": {
      "url": "https://mcp.renor.cloud/mcp",
      "headers": { "Authorization": "Bearer YOUR_RENOR_TOKEN" }
    }
  }
}
```

## Add the memory rule

Agents read memory on their own but save only when told to. Put this in a Trae project rule or user rule:

```text theme={null}
Before a non-trivial decision, call `search` to see what was already decided.
When I decide something, correct you, or state a fact that should outlive this chat, call `note` with the reason.
Before I start a new chat because this one is too long, call `note` with what was decided and what is still open.
At the start of a new chat, call `search` for the project name and the open work before asking me to repeat it.
```

## What was verified

Verified by an automated test: the no-account block starts the Renor server, which saves a fact and finds it again offline.

Not verified: any of this inside the real Trae app. The Trae documentation could not be read when this page was written, so these are not confirmed: that Trae accepts these exact blocks, that a remote server uses `url` with `headers`, the `.trae/mcp.json` path, where Trae reads rules, and whether a hosted sign-in other than a token header works. `npx renor connect --client trae` is not available yet.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.