Nvidia nemoclaw user monitor sandbox
Skill autohandai/community-skills/nvidia-nemoclaw-user-monitor-sandbox
A collection of curated, useful, and safe skills for Autohand Code CLI Agent
npx -y skills add autohandai/community-skills --skill nvidia-nemoclaw-user-monitor-sandboxAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Inspects sandbox health, traces agent behavior, and diagnoses problems. Use when monitoring a running sandbox, debugging agent issues, or checking sandbox logs. Trigger keywords - monitor nemoclaw sandbox, debug nemoclaw agent issues.
The file declares its own license as Apache-2.0 AND CC-BY-4.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
3.6 KB, 788 tokens by cl100k_base, as published. Nobody here has run it
Monitor Sandbox Activity and Debug Issues
Prerequisites
- A running NemoClaw sandbox.
- The OpenShell CLI on your
PATH.
Use the NemoClaw status, logs, and TUI tools together to inspect sandbox health, trace agent behavior, and diagnose problems.
Check Sandbox Health
Run the status command to view the sandbox state, gateway health, and active inference configuration:
$ nemoclaw <name> status
For local Ollama and local vLLM routes, nemoclaw <name> status also probes the host-side health endpoint directly.
This catches a stopped local backend before you retry inference.local from inside the sandbox.
Key fields in the output include the following:
- Sandbox details, which show the configured model, provider, GPU mode, and applied policy presets.
- Gateway and process health, which show whether NemoClaw can still reach the OpenShell gateway and whether the in-sandbox agent process is running.
- Inference health for local Ollama and local vLLM, which shows
healthyorunreachabletogether with the probed local URL. - NIM status, which shows whether a NIM container is running and healthy when that path is in use.
Run nemoclaw <name> status on the host to check sandbox state.
Use openshell sandbox list for the underlying sandbox details.
View Blueprint and Sandbox Logs
Stream the most recent log output from the blueprint runner and sandbox:
$ nemoclaw <name> logs
To follow the log output in real time:
$ nemoclaw <name> logs --follow
Monitor Network Activity in the TUI
Open the OpenShell terminal UI for a live view of sandbox network activity and egress requests:
$ openshell term
For a remote sandbox, SSH to the instance and run openshell term there.
The TUI shows the following information:
- Active network connections from the sandbox.
- Blocked egress requests awaiting operator approval.
- Inference routing status.
Refer to Approve or Deny Agent Network Requests (use the nemoclaw-user-manage-policy skill) for details on handling blocked requests.
Test Inference
Run a test inference request to verify that the provider is responding:
$ nemoclaw my-assistant connect
$ openclaw agent --agent main --local -m "Test inference" --session-id debug
If the request fails, check the following:
- Run
nemoclaw <name> statusto confirm the active provider and endpoint. For local Ollama and local vLLM, check theInferenceline first. If it showsunreachable, restart the local backend before retrying from inside the sandbox. - Run
nemoclaw <name> logs --followto view error messages from the blueprint runner. - Verify that the inference endpoint is reachable from the host.
Related Skills
nemoclaw-user-reference— Troubleshooting (use thenemoclaw-user-referenceskill) for common issues and resolution stepsnemoclaw-user-manage-policy— Approve or Deny Agent Network Requests (use thenemoclaw-user-manage-policyskill) for the operator approval flownemoclaw-user-configure-inference— Switch Inference Providers (use thenemoclaw-user-configure-inferenceskill) to change the active provider