What changed
Canonical packages now publish under the @remnic/* scope. OpenClaw installs should use @remnic/plugin-openclaw. The legacy @joshuaswarren/openclaw-engram package remains available as a compatibility shim.
Same product, same local-first memory model, new name. Remnic is the canonical identity for the memory engine, plugins, CLI, and docs going forward.
Canonical packages now publish under the @remnic/* scope. OpenClaw installs should use @remnic/plugin-openclaw. The legacy @joshuaswarren/openclaw-engram package remains available as a compatibility shim.
Your memory data, config, and tokens continue to work. Existing Engram installs auto-migrate to the new ~/.remnic/ home on first use.
New installs should go straight to the Remnic packages. The old names remain only to bridge the rename window and keep pointing at the same implementation.
@remnic/plugin-openclaw.@remnic/cli and use remnic.@joshuaswarren/openclaw-engram are upgraded to the 9.3.x shim and auto-migrated on first run.engram binary remains available as a forwarder during the v1.x transition window.Do I need to manually move my data? No. The migration path is automatic and idempotent.
Will old links keep working? GitHub and npm compatibility surfaces remain in place during the rename transition.
Why the rename? "Engram" was ambiguous and conflicted with other projects in the AI/ML space. "Remnic" is distinctive, registrable, and works as a standalone identity across every agent surface.
Where can I learn more? Visit the Remnic repository for documentation and source code.