add-mnemon

Installs mnemon persistent graph-based memory into NanoClaw agent containers via Dockerfile and entrypoint changes.

1|Updated May 22, 2026
One-click install
npx skills add https://github.com/roseDwayane/LocalizeAgenticSys --skill add-mnemon-rosedwayane
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-mnemon
Source: https://github.com/roseDwayane/LocalizeAgenticSys/tree/main/nanoclaw/.claude/skills/add-mnemon
Command: npx skills add https://github.com/roseDwayane/LocalizeAgenticSys --skill add-mnemon-rosedwayane

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? NanoClaw agents lose all conversational context when containers restart, forcing users to restate information in every session. This Skill wires the mnemon memory engine into the agent container so agents recall past context before responding and store new insights after each turn. ## Core Features & Use Cases - Container Image Integration: Adds the mnemon binary install layer to the Dockerfile and registers Claude Code memory hooks via mnemon setup in the container entrypoint. - Persistent Memory Storage: Writes memory to the per-agent-group .claude/ mount so it survives container restarts, with commands to locate and reset the host-side storage path. - Structural Test Guards: Ships vitest tests that fail if the Dockerfile install layer or entrypoint wiring is dropped during upgrades. - Use Case: After applying this Skill, have a conversation with your agent, start a new session days later, and reference an earlier topic — the agent surfaces the relevant prior context automatically without you repeating it. ## Quick Start Ask the agent to apply the add-mnemon skill to install persistent memory into the NanoClaw agent container and rebuild the image.

Frequently Asked Questions about add-mnemon

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add persistent memory to a NanoClaw agent?

Apply the add-mnemon skill, which inserts a mnemon binary install layer into container/Dockerfile and a `mnemon setup --target claude-code` line into the entrypoint. Rebuild the image with ./container/build.sh and restart the service to activate memory hooks.

How does mnemon memory persist across container restarts?

MNEMON_DATA_DIR points to /home/node/.claude/mnemon inside the container, which maps to the per-agent-group .claude/ directory on the host. Because the data lives on a mounted volume, memory survives container restarts and rebuilds.

Does mnemon work with non-Claude agent providers?

No. mnemon hooks fire only under --target claude-code, so groups using a different provider such as AGENT_PROVIDER=opencode never invoke the claude CLI and the hooks do not run. Confirm the provider with grep AGENT_PROVIDER before applying.

Why does the container show 'mnemon: command not found'?

This error means the image was not rebuilt after the Dockerfile layer was added. Run ./container/build.sh to rebuild the image, then restart the service so the new binary is available in the running container.

How do I reset or delete an agent's stored memory?

Stop the container, locate the host path with docker inspect filtering for the /home/node/.claude mount destination, then delete the mnemon/ subdirectory from that path. Restarting the container starts memory fresh.