Agent skill / nvidia
Explains operational tasks after the quickstart: listing sandboxes, status and health checks, logs, diagnostics, port forwards, multiple sandboxes, credential reset, rebuilds, network presets, upgrades, and uninstall. Trigger keywords - manage nemoclaw sandboxes, nemoclaw status, nemoclaw list, nemoclaw dashboard port, nemoclaw rebuild, nemoclaw upgrade sandboxes, nemoclaw uninstall, sandbox mutability, sandbox runtime configuration, sandbox rebuild, nemoclaw backup, nemoclaw restore, workspace backup, openshell sandbox download upload, nemoclaw messaging channels, nemoclaw telegram, nemoclaw discord, nemoclaw slack, nemoclaw wechat, nemoclaw whatsapp, openshell channel messaging, nemoclaw workspace files, soul.md, user.md, identity.md, agents.md, sandbox persistence.
Core file
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionnemoclaw-user-manage-sandboxesExecute the skills CLI command in your project's root directory to begin installation:
Package manager
npx skills install nvidia/skills/nemoclaw-user-manage-sandboxesFetches nemoclaw-user-manage-sandboxes from nvidia/skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate nemoclaw-user-manage-sandboxes. Access via /nemoclaw-user-manage-sandboxesin your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Copy the command for your terminal
Package manager
npx skills install nvidia/skills/nemoclaw-user-manage-sandboxesWorks with
| name | "nemoclaw-user-manage-sandboxes" |
| description | "Explains operational tasks after the quickstart: listing sandboxes, status and health checks, logs, diagnostics, port forwards, multiple sandboxes, credential reset, rebuilds, network presets, upgrades, and uninstall. Trigger keywords - manage nemoclaw sandboxes, nemoclaw status, nemoclaw list, nemoclaw dashboard port, nemoclaw rebuild, nemoclaw upgrade sandboxes, nemoclaw uninstall, sandbox mutability, sandbox runtime configuration, sandbox rebuild, nemoclaw backup, nemoclaw restore, workspace backup, openshell sandbox download upload, nemoclaw messaging channels, nemoclaw telegram, nemoclaw discord, nemoclaw slack, nemoclaw wechat, nemoclaw whatsapp, openshell channel messaging, nemoclaw workspace files, soul.md, user.md, identity.md, agents.md, sandbox persistence." |
| license | "Apache-2.0" |
Use this guide after you finish the OpenClaw quickstart (use the nemoclaw-user-get-started skill).
It covers day-two sandbox operations such as listing sandboxes, checking health, managing ports, rebuilding safely, upgrading, and uninstalling.
When a workflow uses the lower-level OpenShell CLI, see CLI Selection Guide (use the nemoclaw-user-reference skill) for the boundary between nemoclaw and openshell.
List every sandbox registered on this host:
$ nemoclaw list
The list shows each sandbox's model, provider, policy presets, active SSH session indicator, and dashboard URL when a dashboard port is recorded. Use JSON output for scripts:
$ nemoclaw list --json
Check a specific sandbox's health, inference route, active connections, live policy, update status, and messaging-channel overlap warnings:
$ nemoclaw my-assistant status
Use the host-level status command when you want the sandbox inventory plus host auxiliary service state, such as cloudflared:
$ nemoclaw status
View recent sandbox logs:
$ nemoclaw my-assistant logs
Stream logs while you reproduce a problem:
$ nemoclaw my-assistant logs --follow
The log command reads both OpenClaw gateway output and OpenShell audit events, so policy denials appear beside gateway logs.
Collect diagnostics for bug reports or support handoff:
$ nemoclaw debug --sandbox my-assistant --output nemoclaw-debug.tar.gz
Use --quick for a smaller local summary:
$ nemoclaw debug --quick --sandbox my-assistant
The debug command gathers system information, Docker state, gateway logs, and sandbox status.
If the forward stopped, or the installer reported that no active forward was found and the URL does not load, restart it manually with the port from the install summary.
$ openshell forward start --background <dashboard-port> my-gpt-claw
To list active forwards across all sandboxes, run the following command.
$ openshell forward list
Each sandbox needs its own dashboard port, since openshell forward refuses to bind a port that another sandbox is already using.
When the default port is already held by another sandbox, nemoclaw onboard scans ports 18789 through 18799 and uses the next free port.
$ nemoclaw onboard # first sandbox uses 18789
$ nemoclaw onboard # second sandbox uses the next free port, such as 18790
To choose a specific port, pass --control-ui-port:
$ nemoclaw onboard --control-ui-port 19000
You can also set CHAT_UI_URL or NEMOCLAW_DASHBOARD_PORT before onboarding:
$ CHAT_UI_URL=http://127.0.0.1:19000 nemoclaw onboard
$ NEMOCLAW_DASHBOARD_PORT=19000 nemoclaw onboard
For full details on port conflicts and overrides, refer to Port already in use (use the nemoclaw-user-reference skill).
Recover from a misconfigured sandbox without re-running the full onboard wizard or destroying workspace state.
Change the active model or provider at runtime without rebuilding the sandbox:
$ nemoclaw inference set --model <model> --provider <provider>
Refer to Switch Inference Providers (use the nemoclaw-user-configure-inference skill) for provider-specific model IDs and API compatibility notes.
If nemoclaw <name> status reports the sandbox is alive but the gateway is not running, run the recover command instead of opening a shell.
$ nemoclaw <sandbox-name> recover
The command restarts the in-sandbox gateway and re-establishes the dashboard port-forward in one step.
It is idempotent and safe to script.
Refer to nemoclaw <name> recover (use the nemoclaw-user-reference skill) for details.
If a provider credential was entered incorrectly during onboarding, clear the gateway-registered value and re-enter it on the next onboard run:
$ nemoclaw credentials list # see which providers are registered
$ nemoclaw credentials reset <PROVIDER> # clear a single provider, for example nvidia-prod
$ nemoclaw onboard # re-run to re-enter the cleared provider
The credentials command is documented in full at nemoclaw credentials reset <PROVIDER> (use the nemoclaw-user-reference skill).
If you changed the underlying Dockerfile, upgraded OpenClaw, or want to pick up a new base image without losing your sandbox's workspace files, use rebuild instead of destroying and recreating:
$ nemoclaw <sandbox-name> rebuild
Rebuild preserves the mounted workspace and registered policies while recreating the container.
If NemoClaw cannot archive any requested state path, it reports the backup failure and stops before deleting the original sandbox.
Refer to nemoclaw <name> rebuild (use the nemoclaw-user-reference skill) for flag details.
Apply an additional preset, such as Telegram or GitHub, to a running sandbox without re-onboarding:
$ nemoclaw <sandbox-name> policy-add
Refer to nemoclaw <name> policy-add (use the nemoclaw-user-reference skill) for usage details and flags.
Non-interactive re-onboards in the default suggested policy mode preserve presets added this way.
To make a re-onboard authoritative, set NEMOCLAW_POLICY_MODE=custom and provide NEMOCLAW_POLICY_PRESETS with the exact list to apply; onboarding removes anything else.
See NEMOCLAW_POLICY_MODE (use the nemoclaw-user-reference skill) for the full table.
When a new NemoClaw release becomes available, update the nemoclaw CLI on your host and check existing sandboxes for stale agent/runtime versions.
Re-run the installer.
Before it onboards anything, the installer calls nemoclaw backup-all (use the nemoclaw-user-reference skill) automatically, storing a snapshot of each running sandbox in ~/.nemoclaw/rebuild-backups/ as a safety net.
If your existing gateway is from OpenShell earlier than 0.0.37, the installer prompts before it runs the new automatic gateway upgrade path.
The automatic path is offered only when the existing nemoclaw CLI supports backup-all; older installs must preserve sandbox state manually before retiring the gateway.
For unattended installs, set NEMOCLAW_ACCEPT_EXPERIMENTAL_OPENSHELL_UPGRADE=1, or manually run nemoclaw backup-all and openshell gateway destroy -g nemoclaw || openshell gateway destroy before rerunning the installer as curl -fsSL https://www.nvidia.com/nemoclaw.sh | NEMOCLAW_OPENSHELL_UPGRADE_PREPARED=1 bash.
$ curl -fsSL https://www.nvidia.com/nemoclaw.sh | bash
The installer checks registered sandboxes after onboarding succeeds and runs nemoclaw upgrade-sandboxes --auto for stale running sandboxes.
Use upgrade-sandboxes directly to verify the result, rebuild when you skipped the installer or onboarding step, or handle sandboxes that were stopped or could not be version-checked.
The upgrade flow is non-destructive by default because NemoClaw preserves manifest-defined workspace state, but a manual snapshot before any major upgrade gives you a state restore point.
$ nemoclaw <sandbox-name> snapshot create --name pre-upgrade # optional, recommended
$ nemoclaw update --yes # updates CLI through the maintained installer flow
$ nemoclaw upgrade-sandboxes --check # verify or list remaining stale/unknown sandboxes
$ nemoclaw upgrade-sandboxes # manually rebuild remaining stale running sandboxes
nemoclaw update is the CLI wrapper around the same installer path as curl -fsSL https://www.nvidia.com/nemoclaw.sh | bash.
Use nemoclaw update --check when you only want to inspect version state and see the maintained update command.
For scripted manual rebuilds, use nemoclaw upgrade-sandboxes --auto to skip the confirmation prompt.
If the upgraded sandbox needs its workspace state reverted, restore the pre-upgrade snapshot into the running sandbox. This restores saved state directories only; it does not downgrade the sandbox image or agent/runtime:
$ nemoclaw <sandbox-name> snapshot restore pre-upgrade
Load references/lifecycle-details.md for detailed steps on What Changes During a Rebuild.
To remove NemoClaw and all resources created during setup, run the CLI's built-in uninstall command:
nemoclaw uninstall
| Flag | Effect |
|---|---|
--yes | Skip the confirmation prompt. |
--keep-openshell | Leave OpenShell binaries installed. |
--delete-models | Also remove NemoClaw-pulled Ollama models. |
nemoclaw uninstall runs the version-pinned uninstall.sh that shipped with your installed CLI, so it does not fetch anything over the network at uninstall time.
If the nemoclaw CLI is missing or broken, fall back to the hosted script:
curl -fsSL https://raw.githubusercontent.com/NVIDIA/NemoClaw/refs/heads/main/uninstall.sh | bash
The same --yes, --keep-openshell, and --delete-models flags listed above also apply to the hosted script. Pass them after bash -s --.
curl -fsSL https://raw.githubusercontent.com/NVIDIA/NemoClaw/refs/heads/main/uninstall.sh | bash -s -- --yes --delete-models
For a full comparison of the two forms, including what they fetch, what they trust, and when to prefer each, see nemoclaw uninstall vs. the hosted uninstall.sh (use the nemoclaw-user-reference skill).
SOUL.md, USER.md, IDENTITY.md, AGENTS.md, or other workspace files, or when preparing to back up or restore workspace state. Explains what workspace personality and configuration files are, where they live, and how they persist across sandbox restarts.nemoclaw-user-monitor-sandbox — Monitor Sandbox Activity (use the nemoclaw-user-monitor-sandbox skill) for observability toolsPrerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
nvidia/skills
nvidia/skills
nvidia/skills
nvidia/skills
nvidia/skills
nvidia/skills
Keeps context tight: nemoclaw-user-manage-sandboxes is the kind of skill you can hand to a new teammate without a long onboarding doc.
Keeps context tight: nemoclaw-user-manage-sandboxes is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added nemoclaw-user-manage-sandboxes from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
We added nemoclaw-user-manage-sandboxes from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
nemoclaw-user-manage-sandboxes has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: nemoclaw-user-manage-sandboxes is focused, and the summary matches what you get after install.
nemoclaw-user-manage-sandboxes fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
nemoclaw-user-manage-sandboxes fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
nemoclaw-user-manage-sandboxes reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend nemoclaw-user-manage-sandboxes for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 71