> For the complete documentation index, see [llms.txt](https://evo-5.gitbook.io/evo/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://evo-5.gitbook.io/evo/resources/migrating.md).

# Migrating from evo-memory

If you used the previous package name `evo-memory`, migration is automatic. This page documents the compatibility surface.

## What Changed

| Component      | Old                       | New                          |
| -------------- | ------------------------- | ---------------------------- |
| Package name   | `evo-memory`              | `evo`                        |
| Plugin rows    | `evo-memory/cordis`, etc. | `evo/cordis`, `evo/deepseek` |
| Web carrier    | —                         | `evo-web` (bare name)        |
| Service key    | `ctx.evoMemory`           | `ctx.evo`                    |
| HTTP prefix    | `/evo-memory/*`           | `/evo/*`                     |
| Data directory | `evo-memory/`             | `evo/`                       |

## Compatibility Surface

### Database

If the platform default `evo/` directory has no `memory.db` but the pre-rename `evo-memory/` directory does, evo automatically uses the old file.

Move it to the new directory whenever convenient:

```bash
# macOS
mv ~/Library/Application\ Support/evo-memory/memory.db \
   ~/Library/Application\ Support/evo/memory.db

# Linux
mv ~/.local/share/evo-memory/memory.db \
   ~/.local/share/evo/memory.db
```

### Environment Variables

Old variables are still read, after their new counterparts:

| Legacy                | Current        |
| --------------------- | -------------- |
| `EVO_MEMORY_DATA_DIR` | `EVO_DATA_DIR` |
| `EVO_MEMORY_PROVIDER` | `EVO_PROVIDER` |
| `EVO_MEMORY_MODEL`    | `EVO_MODEL`    |

### HTTP API

The old path prefix `/evo-memory/*` is mounted alongside `/evo/*`. Both work identically.

## Required Changes

### Plugin Configuration

Update your `cordis.patch.yml`:

```yaml
# Old
- id: evo-memory
  name: evo-memory/cordis
  config: {}

- id: evo-memory-deepseek
  name: evo-memory/deepseek
  config:
    provider: deepseek-official
    model: deepseek-chat

# New
- id: evo
  name: evo/cordis
  config: {}

- id: evo-deepseek
  name: evo/deepseek
  config:
    provider: deepseek-official
    model: deepseek-chat

- id: evo-web
  name: evo
  config: {}
```

### Service Usage

Update any code using the service:

```ts
// Old
await ctx.evoMemory.remember({ ... })
await ctx.evoMemory.recall({ ... })

// New
await ctx.evo.remember({ ... })
await ctx.evo.recall({ ... })
```

### Installers

Re-run the appropriate installer to update hook configurations:

```bash
# DeepSeek Harness
./install_evo_dsps.sh

# Claude Code
./install_evo_claude.sh

# Codex
./install_evo_codex.sh
```

## No Data Migration Needed

Your existing memories are preserved. The database schema hasn't changed — only the package name and default paths.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://evo-5.gitbook.io/evo/resources/migrating.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.