Commands
NemoClaw provides two command interfaces.
The plugin commands run under the openclaw nemoclaw namespace inside the OpenClaw CLI.
The standalone nemoclaw binary handles host-side setup, deployment, and service management.
Both interfaces are installed when you run npm install -g nemoclaw.
Plugin Commands
openclaw nemoclaw launch
Bootstrap OpenClaw inside an OpenShell sandbox.
If NemoClaw detects an existing host installation, launch stops unless you pass --force.
$ openclaw nemoclaw launch [--force] [--profile <profile>]
--force
Skip the ergonomics warning and force plugin-driven bootstrap. Without this flag,
NemoClaw recommends using openshell sandbox create directly for new installs.
--profile <profile>
Blueprint profile to use. Default: default.
nemoclaw <name> connect
Open an interactive shell inside the OpenClaw sandbox. Use this after launch to connect and chat with the agent through the TUI or CLI.
$ nemoclaw my-assistant connect
If the TUI view is not a good fit for very long responses, use the CLI form instead:
$ openclaw agent --agent main --local -m "<prompt>" --session-id <id>
This is the recommended workaround when you need the full response printed directly in the terminal.
openclaw nemoclaw status
Display sandbox health, blueprint run state, and inference configuration.
$ openclaw nemoclaw status [--json]
--json
Output as JSON for programmatic consumption.
When running inside an active OpenShell sandbox, the status command detects the sandbox context and reports “active (inside sandbox)” instead of false negatives.
Host-side sandbox state and inference configuration are not inspectable from inside the sandbox.
Run openshell sandbox list on the host to check the underlying sandbox state.
openclaw nemoclaw logs
Stream blueprint execution and sandbox logs.
$ openclaw nemoclaw logs [-f] [-n <count>] [--run-id <id>]
-f, --follow
Follow log output, similar to tail -f.
-n, --lines <count>
Number of lines to show. Default: 50.
--run-id <id>
Show logs for a specific blueprint run instead of the latest.
/nemoclaw Slash Command
The /nemoclaw slash command is available inside the OpenClaw chat interface for quick actions:
| Subcommand | Description |
|---|---|
/nemoclaw status | Show sandbox and inference state |
Standalone Host Commands
The nemoclaw binary handles host-side operations that run outside the OpenClaw plugin context.
nemoclaw onboard
Run the interactive setup wizard. The wizard creates an OpenShell gateway, registers inference providers, builds the sandbox image, and creates the sandbox. Use this command for new installs and for recreating a sandbox after changes to policy or configuration.
$ nemoclaw onboard
The first run prompts for your NVIDIA API key and saves it to ~/.nemoclaw/credentials.json.
The wizard prompts for a sandbox name. Names must follow RFC 1123 subdomain rules: lowercase alphanumeric characters and hyphens only, and must start and end with an alphanumeric character. Uppercase letters are automatically lowercased.
Before creating the gateway, the wizard runs preflight checks.
On systems with cgroup v2 (Ubuntu 24.04, DGX Spark, WSL2), it verifies that Docker is configured with "default-cgroupns-mode": "host" and provides fix instructions if the setting is missing.
nemoclaw list
List all registered sandboxes with their model, provider, and policy presets.
$ nemoclaw list
nemoclaw deploy
Warning: The
nemoclaw deploycommand is experimental and may not work as expected.
Deploy NemoClaw to a remote GPU instance through Brev. The deploy script installs Docker, NVIDIA Container Toolkit if a GPU is present, and OpenShell on the VM, then runs the nemoclaw setup and connects to the sandbox.
$ nemoclaw deploy <instance-name>
nemoclaw <name> connect
Connect to a sandbox by name.
$ nemoclaw my-assistant connect
nemoclaw <name> status
Show sandbox status, health, and inference configuration.
$ nemoclaw my-assistant status
nemoclaw <name> logs
View sandbox logs.
Use --follow to stream output in real time.
$ nemoclaw my-assistant logs [--follow]
nemoclaw <name> destroy
Stop the NIM container and delete the sandbox. This removes the sandbox from the registry.
$ nemoclaw my-assistant destroy
nemoclaw <name> policy-add
Add a policy preset to a sandbox. Presets extend the baseline network policy with additional endpoints.
$ nemoclaw my-assistant policy-add
nemoclaw <name> policy-list
List available policy presets and show which ones are applied to the sandbox.
$ nemoclaw my-assistant policy-list
openshell term
Open the OpenShell TUI to monitor sandbox activity and approve network egress requests. Run this on the host where the sandbox is running.
$ openshell term
For a remote Brev instance, SSH to the instance and run openshell term there, or use a port-forward to the gateway.
nemoclaw start
Start auxiliary services, such as the Telegram bridge and cloudflared tunnel.
$ nemoclaw start
Requires TELEGRAM_BOT_TOKEN for the Telegram bridge.
nemoclaw stop
Stop all auxiliary services.
$ nemoclaw stop
nemoclaw status
Show the sandbox list and the status of auxiliary services.
$ nemoclaw status
nemoclaw setup-spark
Set up NemoClaw on DGX Spark.
This command applies cgroup v2 and Docker fixes required for Ubuntu 24.04.
Run with sudo on the Spark host.
After the fixes complete, the script prompts you to run nemoclaw onboard to continue setup.
$ sudo nemoclaw setup-spark