Engram to Remnic, three months later

In April we renamed Engram to Remnic. Renames are easy to announce and slow to finish, so here is an honest accounting of where things stand three months in.

What moved cleanly

The npm scope is @remnic. The CLI binary is remnic. MCP tools have canonical remnic.* names. The operator console lives at /remnic/ui/. In-chat commands are /remnic. New documentation and this site teach the new names exclusively.

What still answers to the old name

Three surfaces keep the old name because they are real, running interfaces, not cosmetic leftovers:

1. HTTP REST routes live under the /engram/v1/ prefix. Existing clients depend on those paths, so they stay until a versioned migration ships.
2. The OpenClaw gateway CLI namespace is openclaw engram. That is the actual command surface today.
3. Legacy engram.* MCP tool aliases and the engram CLI forwarder remain registered during the v1.x compatibility window, so nothing you scripted in March broke in April.

The principle

We would rather teach you a real endpoint with an old name than a fake endpoint with a new one. Every place the old name survives on this site is one of those real surfaces, marked with a link to the rename notice.

The compatibility window closes with the next major version line. Until then, both names work, one name is taught, and the migration guide covers the details if you have scripts to update.