NemoClaw's sandbox blocks memory
One command fixes it.

The sandbox problem

One command. That's it.

Installs the plugin, configures your key, applies the egress policy, and restarts the gateway.

$ npx @memoryrouter/nemoclaw setup \
  --sandbox my-assistant \
  --api-key <your-memory-key>

$ openclaw mr upload
# Your AI wakes up already knowing everything you've ever talked about.

How it works under the hood

The setup command reads your sandbox's current network policy via openshell sandbox get, merges in the MemoryRouter egress block, and re-applies the full policy via openshell policy set. Idempotent, running it twice won't duplicate anything.

What gets added to your sandbox policy

Minimal egress rule. Only allows GET and POST to api.memoryrouter.ai:443. Scoped to the OpenClaw and Node binaries.

network_policies:
  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/node

Why cloud memory in a sandbox?

NemoClaw's sandbox restricts filesystem writes to /sandbox/.openclaw-data and /tmp. Local vector databases won't survive sandbox rebuilds. Cloud memory persists through everything, sandbox restarts, onboard cycles, policy resets.

CLI reference

Manual setup

Prefer to do it yourself? Here are the individual steps:

Pricing

14-day free trial on every plan. BYOK, no inference markup. See full pricing

FAQ