nemoclaw-user-manage-sandboxes
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
- 最近更新
- 2026-11-10
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- nemoclaw-user-manage-sandboxes
- license
- Apache-2.0
- 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.
02 资源文件 9
- 参考文档BENCHMARK.md3.2 KB
- 参考文档evals/evals.json8.4 KB
- 参考文档references/backup-restore.md6.7 KB
- 参考文档references/lifecycle-details.md2.4 KB
- 参考文档references/messaging-channels.md19.8 KB
- 参考文档references/runtime-controls.md4.7 KB
- 参考文档references/workspace-files.md4.4 KB
- 参考文档skill-card.md2.7 KB
- 其他skill.oms.sig5.7 KB
03 SKILL.md 正文
<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. --> <!-- SPDX-License-Identifier: Apache-2.0 -->
Manage Sandbox Lifecycle
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 Sandboxes
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 Sandbox Health
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
Inspect Logs
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
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.
Manage Dashboard Ports
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
Run Multiple Sandboxes
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).
Reconfigure or Recover
Recover from a misconfigured sandbox without re-running the full onboard wizard or destroying workspace state.
Change Inference Model or API
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.
Restart the Gateway and Port Forward
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.
Reset a Stored Credential
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).
Rebuild a Sandbox While Preserving Workspace State
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.
Add a Network Preset After Onboarding
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.
Update to the Latest Version
When a new NemoClaw release becomes available, update the nemoclaw CLI on your host and check existing sandboxes for stale agent/runtime versions.
Update the NemoClaw CLI
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
Upgrade Sandboxes with Stale Agent and Runtime Versions
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.
Uninstall
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).
References
- references/runtime-controls.md — Single page that answers what can change at runtime versus what requires a rebuild for NemoClaw sandboxes.
- Load references/backup-restore.md when downloading workspace files from a sandbox, uploading restored files into a new sandbox, or preserving sandbox state across rebuilds. Backs up and restores OpenClaw workspace files before destructive operations such as sandbox rebuilds.
- Load references/messaging-channels.md when setting up messaging channels, chat interfaces, or integrations without relying on nemoclaw tunnel start for bridges. Explains how Telegram, Discord, Slack, WeChat, and WhatsApp reach sandboxed OpenClaw and Hermes agents through OpenShell-managed processes and NemoClaw channel commands.
- Load references/workspace-files.md when users ask about
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. - Load references/lifecycle-details.md when you need detailed steps for What Changes During a Rebuild.
Related Skills
- Set Up Messaging Channels to connect Telegram, Discord, or Slack.
- Workspace Files for persistent OpenClaw files inside the sandbox.
- Backup and Restore for snapshot and restore workflows.
nemoclaw-user-monitor-sandbox— Monitor Sandbox Activity (use thenemoclaw-user-monitor-sandboxskill) for observability tools
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.