OpenClaw

OpenClaw is the agent gateway / orchestrator. The MemClaw plugin claims its memory slot — meaning every agent that runs through the gateway gets the same memclaw_* tools, the same backing store, and the same governance rules, with no per-agent setup.

Install

On the gateway host (URL auto-targets this deployment):

curl -s -H "X-API-Key: $MEMCLAW_API_KEY" \
"https://memclaw.net/api/v1/install-plugin?fleet_id=$FLEET_ID" | bash

What this does (manual fallback if you prefer):

1. Downloads plugin source files into ~/.openclaw/plugins/memclaw/
2. Runs npm install && npm run build
3. Edits ~/.openclaw/openclaw.json to:
   • Claim the memory slot
   • Disable the default memory-core plugin
   • Allowlist the memclaw_* tools
4. Writes MEMCLAW_API_KEY, MEMCLAW_FLEET_ID, and MEMCLAW_API_URL into the plugin's .env

Then restart the gateway:

openclaw gateway restart
# or: systemctl --user restart openclaw-gateway

Verify

Within 60 seconds, the gateway should appear in the Fleet Management page on your MemClaw dashboard. From there you can monitor heartbeats, trust levels, and per-agent memory writes.

Why use the gateway path

• One plugin install covers an arbitrary number of agents
• Per-agent memory isolation is automatic (each agent gets its own agent_id)
• Fleet-wide trust and governance — the architect's memories stay above the junior agents'
• Heartbeat-based health monitoring + auto-disable on misbehavior