nemoclaw-user-monitor-sandbox
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.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-10
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- nemoclaw-user-monitor-sandbox
- license
- Apache-2.0
- description
- 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.
02 资源文件 4
- 参考文档BENCHMARK.md2.8 KB
- 参考文档evals/evals.json1.7 KB
- 参考文档skill-card.md2.5 KB
- 其他skill.oms.sig4.5 KB
03 SKILL.md 正文
<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. --> <!-- SPDX-License-Identifier: Apache-2.0 -->
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 -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
04 同仓库更多 Skills
vercel-sandbox
Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.
slack
Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.
electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
dogfood
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.