@memoryrouter/nemoclaw
v0.1.0
Published
One-command setup for MemoryRouter persistent memory on NemoClaw sandboxes — installs the plugin, applies the OpenShell egress policy, and configures your API key
Downloads
17
Maintainers
Readme
@memoryrouter/nemoclaw
One-command persistent memory for NemoClaw sandboxed agents using MemoryRouter.
Quick Start
npx @memoryrouter/nemoclaw setup \
--sandbox my-assistant \
--api-key mk_YOUR_KEY_HEREGet a free API key (50M tokens included) at memoryrouter.ai.
What It Does
NemoClaw runs OpenClaw inside a deny-by-default sandbox. Every outbound network request is blocked unless explicitly allowed. This tool automates the full setup in one command:
- Installs the
mr-memoryplugin viaopenclaw plugins install - Configures your API key in
~/.openclaw/openclaw.json - Applies the MemoryRouter egress rule to your sandbox's network policy
- Restarts the OpenClaw gateway
After setup, your agent automatically stores and recalls conversations across sessions.
Output
memoryrouter-nemoclaw setup
────────────────────────────────────────
[0] Preflight checks...
✓ openshell found
✓ openclaw found
[1] Installing mr-memory plugin...
✓ Plugin installed
[2] Configuring MemoryRouter in ~/.openclaw/openclaw.json...
✓ API key configured
[3] Applying MemoryRouter egress policy to sandbox "my-assistant"...
✓ Policy applied to sandbox "my-assistant"
[4] Restarting OpenClaw gateway...
✓ Gateway restarted
────────────────────────────────────────
✓ Setup complete!CLI Options
Required:
--sandbox <name> NemoClaw sandbox name
--api-key <key> MemoryRouter API key
Optional:
--skip-policy Skip the openshell egress policy update
--skip-plugin-install Skip openclaw plugins install
--dry-run Preview changes without executing
--help Show this helpHow It Works
The Problem
NemoClaw's OpenShell sandbox blocks all outbound traffic by default. The mr-memory plugin installs fine (npm registry is allowed), but when it tries to call api.memoryrouter.ai at runtime — blocked. Silent failure.
The Solution
This package reads your sandbox's current network policy, merges in the MemoryRouter egress rule, and re-applies it via openshell policy set. The egress rule allows:
memoryrouter:
name: memoryrouter
endpoints:
- host: api.memoryrouter.ai
port: 443
protocol: rest
tls: terminate
enforcement: enforce
rules:
- allow: { method: GET, path: /** }
- allow: { method: POST, path: /** }
binaries:
- path: /usr/local/bin/openclaw
- path: /usr/local/bin/nodeManual Setup
If you prefer to apply steps yourself:
- Install:
openclaw plugins install mr-memory - Configure:
openclaw mr mk_YOUR_KEY_HERE - Add the egress YAML above to your sandbox policy
- Apply:
openshell policy set <sandbox> --policy /path/to/policy.yaml --wait - Restart:
openclaw gateway restart
Verify
After a conversation, check logs:
grep MemoryRouter ~/.openclaw/logs/gateway.log | tail -5Test memory:
- Tell your agent something:
"My favorite color is blue" - Start a new session
- Ask:
"What's my favorite color?"
License
MIT
