ClawMetry automatically detects NemoClaw — NVIDIA's enterprise security wrapper for OpenClaw that runs agents inside sandboxed OpenShell containers.
No extra configuration is needed in most cases. The sync daemon auto-discovers session files whether they live in ~/.openclaw/ on the host or inside an OpenShell container.
ClawMetry detects NemoClaw in two ways:
- Binary detection — checks for the
nemoclawCLI and runsnemoclaw statusto get sandbox info - Container detection — scans running Docker containers for
openshell,nemoclaw, orghcr.io/nvidia/images, then reads sessions via volume mounts ordocker cp
Session files synced from NemoClaw containers are tagged with runtime=nemoclaw and container_id metadata in the cloud dashboard, so you can tell them apart from standard OpenClaw sessions at a glance.
For the best experience, run ClawMetry's sync daemon on the host machine (not inside the sandbox). This avoids NemoClaw network policy restrictions.
# On the host (outside the sandbox)
pip install clawmetry
clawmetry connect
clawmetry syncThe sync daemon will automatically find sessions inside any running OpenShell containers.
If auto-detection doesn't work, point ClawMetry at the right sandbox:
export NEMOCLAW_SANDBOX=my-sandbox-name
clawmetry syncIf you must run the sync daemon inside the OpenShell sandbox, add this egress rule to your NemoClaw network policy so it can reach the ClawMetry ingest API:
# nemoclaw-policy.yaml
network:
egress:
- host: ingest.clawmetry.com
port: 443
protocol: httpsApply with:
nemoclaw policy apply --file nemoclaw-policy.yaml| Endpoint | Port | Protocol | Required |
|---|---|---|---|
ingest.clawmetry.com |
443 | HTTPS | Yes (sync daemon → cloud) |
localhost:8900 |
8900 | HTTP | Yes (local dashboard UI) |
Docker socket (/var/run/docker.sock) |
— | Unix socket | For container session discovery |
The sync daemon only makes outbound HTTPS calls to ingest.clawmetry.com. No inbound ports are required.