Skip to main content

​
Operations and Troubleshooting

Use the MemantoClaw status, logs, and TUI tools together to inspect sandbox health and trace agent behavior.

​
Monitor Sandbox Activity

​
Check Health

memantoclaw ``<name>`` status
This probes the gateway health, process health, and tests local Ollama/vLLM routes directly.

​
View Logs

memantoclaw ``<name>`` logs --follow

​
Open TUI

openshell term
Use this to view active network connections and approve/deny blocked egress requests.

​
Troubleshooting Common Issues

  • Installer fails on Node.js: MemantoClaw requires Node.js 22.16+. Install it using nvm use 22.
  • Docker permission denied: Ensure your user is in the docker group (sudo usermod -aG docker $USER).
  • OOM errors during sandbox creation: Image push requires memory. Add at least 8 GB of swap file on smaller machines.
  • Port already in use: The gateway uses port 18789. Terminate conflicting processes (sudo lsof -i :18789).
  • Sandbox lost after gateway restart: Upgrade OpenShell to >= 0.0.24 via memantoclaw onboard.
  • Inference unreachable: Check if Ollama/vLLM is running. Increase timeout (MEMANTOCLAW_LOCAL_INFERENCE_TIMEOUT=300) for slow hardware.
Generate a debug tarball for support if needed: 
memantoclaw debug

​
Agent Skills for AI Coding Assistants

MemantoClaw ships agent skills generated directly from documentation. These allow coding assistants (like Cursor, Claude Code) to read project-specific guidance. Fetch the skills via sparse checkout: 
git clone --filter=blob:none --no-checkout https://github.com/moorcheh-ai/memantoclaw.git
cd memantoclaw
git sparse-checkout set --no-cone '/.agents/skills/**'
git checkout
Open the directory in your assistant to give it deep context on managing your sandbox.
For complete, unabridged technical details on this topic, refer to the official NVIDIA NemoClaw Documentation. Portions of this guide are summarized and adapted from NVIDIA Corporation (Copyright © 2026), licensed under the Apache License, Version 2.0.