> This page is for version Latest (default).
> For other versions, use one of these documentation indexes:
> - Latest (default): https://docs.nvidia.com/nemoclaw/latest/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/nemoclaw/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/nemoclaw/_mcp/server.

## v0.0.126

NemoClaw v0.0.126 moves sandbox, gateway, and host-forward recovery onto typed OpenShell lifecycle controls.
It also strengthens Podman onboarding, destructive-operation safety, secret redaction, policy activation, and package execution.

* Sandbox lifecycle and host-forward operations now share typed OpenShell adapters for selection, registration, observation, recovery, and cleanup.
  Stop, destroy, and rebuild retain the local sandbox registry record when forward release cannot be proved.
  Gateway startup offers a service stop command only when one stable active service is the sole listener and owns the selected state, and supported recovery no longer replaces legacy keepalive containers.
  Related changes: [PR #11594](https://github.com/NVIDIA/NemoClaw/pull/11594), [PR #11725](https://github.com/NVIDIA/NemoClaw/pull/11725), [PR #11741](https://github.com/NVIDIA/NemoClaw/pull/11741), and [PR #11776](https://github.com/NVIDIA/NemoClaw/pull/11776).
  For more information, refer to [Understand Gateway Lifecycle Control](/user-guide/openclaw/manage-sandboxes/configure-sandboxes/understand-gateway-lifecycle-control) and [Recover and Rebuild Sandboxes](/user-guide/openclaw/manage-sandboxes/operate-sandboxes/recover-and-rebuild-sandboxes).
* `nemoclaw <name> recover` now starts a stopped Docker-driver sandbox through OpenShell so the sandbox returns to `Ready` instead of leaving a running container in `Stopped`.
  A later `start` repairs the same phase mismatch, while paused sandboxes and running sandboxes in other phases remain unchanged.
  Related changes: [PR #11784](https://github.com/NVIDIA/NemoClaw/pull/11784) and [PR #11797](https://github.com/NVIDIA/NemoClaw/pull/11797).
  For more information, refer to [Recover and Rebuild Sandboxes](/user-guide/openclaw/manage-sandboxes/operate-sandboxes/recover-and-rebuild-sandboxes) and [Recover and Rebuild Sandboxes for Hermes](/user-guide/hermes/manage-sandboxes/operate-sandboxes/recover-and-rebuild-sandboxes).
* Managed Podman onboarding now reads the structured OpenShell main-process specification, preserves its terminal setting, and releases the stopped original container before the replacement binds its port.
  Failed-onboarding destroy uses the explicitly selected Podman provider only before durable sandbox or gateway provider state exists, and it does not fall through to Docker.
  Related change: [PR #11816](https://github.com/NVIDIA/NemoClaw/pull/11816).
  For more information, refer to [Platform Support](/user-guide/openclaw/reference/platform-support) and the [NemoClaw CLI Commands Reference](/user-guide/openclaw/reference/commands).
* `rebuild` now stops before backup or sandbox deletion when a recorded remote inference credential is expired, missing, or cannot be verified.
  It checks the credential again immediately before deletion, preserves the existing sandbox, and does not let `--force` bypass this boundary.
  Related change: [PR #11779](https://github.com/NVIDIA/NemoClaw/pull/11779).
  For more information, refer to [Recover and Rebuild Sandboxes](/user-guide/openclaw/manage-sandboxes/operate-sandboxes/recover-and-rebuild-sandboxes).
* `nemoclaw uninstall --yes` can now remove a non-default-port state root left by onboarding that failed during preflight before it created a sandbox or gateway.
  Cleanup holds the onboarding lock, revalidates ownership and absence, and preserves state when the evidence changes, belongs to another gateway, or uses a custom state root.
  Related change: [PR #11602](https://github.com/NVIDIA/NemoClaw/pull/11602).
  For more information, refer to [Uninstall NemoClaw](/user-guide/openclaw/manage-sandboxes/operate-sandboxes/uninstall-nemoclaw).
* OpenShell policy writes now allow 65 seconds for the 60-second activation wait and process settlement, while read-only policy operations retain their 15-second deadline.
  This prevents larger policy updates, including a second managed MCP server, from ending before OpenShell reports the activation result.
  Related change: [PR #11863](https://github.com/NVIDIA/NemoClaw/pull/11863).
  For more information, refer to [Apply Policy Presets](/user-guide/openclaw/network-policy/configure-policies/apply-policy-presets) and [Manage MCP Servers](/user-guide/openclaw/manage-sandboxes/mcp-servers/manage-mcp-servers).
* `nemoclaw list` now applies the same redaction boundary as `nemoclaw status` to sandbox, inference, policy, agent, phase, and recovery fields in text and JSON output.
  Managed vLLM adoption now queries the published port by the inspected container ID, so a container-name transfer cannot redirect the adoption decision.
  Related changes: [PR #11815](https://github.com/NVIDIA/NemoClaw/pull/11815) and [PR #11821](https://github.com/NVIDIA/NemoClaw/pull/11821).
  For more information, refer to the [NemoClaw CLI Commands Reference](/user-guide/openclaw/reference/commands) and [Set Up vLLM](/user-guide/openclaw/inference/local-inference/set-up-vllm).
* Managed image and CI builds use Node.js 24.18.1 with integrity-verified npm 12.0.2 while the public Node.js 22.19 compatibility floor remains unchanged.
  Builds also set every `package.json` executable, including `nemoclaw-acp` and `nemoclaw-blueprint-runner`, to mode `0755`, so fresh packages can invoke them directly.
  Related changes: [PR #11736](https://github.com/NVIDIA/NemoClaw/pull/11736), [PR #11839](https://github.com/NVIDIA/NemoClaw/pull/11839), and [PR #11840](https://github.com/NVIDIA/NemoClaw/pull/11840).
  For more information, refer to [Quickstart with Hermes](/user-guide/hermes/get-started/quickstart) and [Troubleshooting](/user-guide/hermes/reference/troubleshooting).
* The Experimental NemoCUA command reference now states that host-local inference, including local Ollama, is unsupported and names the onboarding error for that selection.
  Related change: [PR #11095](https://github.com/NVIDIA/NemoClaw/pull/11095).
  For more information, refer to the [NemoClaw CLI Commands Reference](/user-guide/openclaw/reference/commands).