nemoclaw-user-monitor-sandbox

Diagnose failing NemoClaw sandboxes via health, logs, and live network activity.

Updated May 23, 2026
One-click install
npx skills add https://github.com/yo-steven/skills-exploration-20260522 --skill nemoclaw-user-monitor-sandbox-yo-steven
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nemoclaw-user-monitor-sandbox
Source: https://github.com/yo-steven/skills-exploration-20260522/tree/main/skills/NemoClaw/nemoclaw-user-monitor-sandbox
Command: npx skills add https://github.com/yo-steven/skills-exploration-20260522 --skill nemoclaw-user-monitor-sandbox-yo-steven

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly identify why a running NemoClaw sandbox is unhealthy or why an agent is misbehaving by inspecting status, logs, and live network activity.

Core Features & Use Cases

  • Sandbox health inspection: Checks sandbox state, gateway/process reachability, inference health for local Ollama and vLLM routes, and NIM container status.
  • Log-driven debugging: Streams blueprint runner and sandbox logs to pinpoint failures and error messages.
  • Live network monitoring: Uses the OpenShell TUI to observe connections, blocked egress requests awaiting operator approval, and inference routing behavior.
  • Use Case: When an agent appears stuck or inference requests fail, use health checks and logs to confirm whether the provider endpoint is reachable, then use the TUI to see which egress requests are blocked or misrouted.

Quick Start

Run nemoclaw <name> status to verify sandbox health, inference reachability, and gateway/process health before deeper log and network inspection.

Frequently Asked Questions about nemoclaw-user-monitor-sandbox

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose a failing NemoClaw sandbox?

To diagnose a failing NemoClaw sandbox, inspect sandbox status, stream blueprint runner logs, and monitor live network activity using the OpenShell TUI to identify health, routing, and operational failures.

Why does my local inference route fail inside a sandbox?

Local inference route failures occur when the provider endpoint is unreachable. Use sandbox health checks to verify Ollama, vLLM, and NIM container status, then inspect logs for misrouted or blocked egress requests.

How do I monitor blocked network egress requests for an agent?

You monitor blocked network egress requests by launching the OpenShell TUI, which surfaces live connections, operator approval queues, and inference routing behavior for running sandboxes.

Do I need OpenShell CLI to debug sandbox logs?

Yes, you need the OpenShell CLI and a running NemoClaw sandbox. The CLI provides the term TUI and log streaming capabilities required to inspect blueprint runner output and pinpoint agent errors.

What is the best way to troubleshoot an agent that appears stuck?

The best way to troubleshoot a stuck agent is running a sandbox health check to confirm gateway and process reachability, then streaming sandbox logs to pinpoint the exact failure or blocked egress request.