NemoClaw v0.0.120 is out

[cjagwani]

NemoClaw v0.0.120 is out

NemoClaw v0.0.120 makes deployed sandboxes easier to inspect and recover. The release adds secret-free configuration export, a global system doctor, and more reliable onboarding across managed snapshots, native Podman, N1x, vLLM, and plain-sandbox setups.

This release also tightens lifecycle and trust boundaries. Managed host forwarding now uses OpenShell service forwarding, recovery retains the sandbox's recorded authority, unsafe Model Context Protocol (MCP) projections are rejected, and messaging provider refresh and recovery fail closed without discarding a working credential.

Hermes users get the supported 0.20.6 runtime plus faster, more predictable Portable recovery. Existing installations that still contain legacy Shields state will receive explicit quarantine and rebuild guidance because Shields is no longer part of NemoClaw core.

Configuration and onboarding

• nemoclaw config export <sandbox> --output <path|-> produces a canonical nemoclaw.nvidia.com/v1 document after cross-checking the sandbox's registry, lifecycle, gateway, workload, image, inference, policy, and credential-reference state. Output excludes credential values and fails closed on inconsistent evidence. On Linux, file output is owner-only and atomic, giving operators a durable record for audit and comparison. #11015
• nemoclaw doctor performs read-only host and gateway checks without requiring a selected sandbox. Human-readable and redacted JSON reports make readiness failures easier to diagnose before onboarding, while required failures still return a nonzero status. #11012
• Onboarding now restores validated managed snapshots before registering replacements, supports native Docker-less Podman readiness, keeps qualified N1x users in the standard provider flow when they decline the Deferred N1x Express preview, preserves the served vLLM model from resume state, and prevents plain sandboxes without a Portable receipt from entering the Hermes lifecycle-lock path. Together, these changes reduce partial registrations and incorrect provider assumptions. #10690 #10900 #11046 #10882 #10864

Lifecycle and recovery

• Managed dashboard, messaging, and MCP forwards now use detached openshell forward service processes. Port ownership, reachability, gateway availability, workspace selection, TLS, and mTLS authority are checked against the sandbox's recorded state, so recovery no longer depends on ambient selectors or NemoClaw-owned SSH forwarding receipts. #10695 #10814 #10815 #10810
• Hermes Portable recovery reuses validated Podman and executable evidence within each lifecycle transaction, performs one bounded in-sandbox readiness wait, and retries only transient final readiness-publication failures. Coordinated host-forward settlement and in-process TCP checks shorten the recovery path without weakening authority checks, health validation, or rollback. #10927 #10983 #10988 #10999 #11019
• Shields has been removed from NemoClaw core. Upgrades preserve and report legacy Shields state, then stop with quarantine and rebuild guidance instead of interpreting or deleting it; legacy OpenClaw migration also retains the prepared rebuild context and exact managed-image choice. #10722 #10996

Agent runtimes and inference

• The supported managed Hermes runtime is now 0.20.6, including retargeted compatibility patches, reviewed lazy Hindsight dependencies, workspace-aware session previews, and scheduled-task recovery. Gateway startup preserves the validated lazy-install target, while legacy rebuilds without an image hint require the release-pinned immutable Hermes base before mutation. #10595 #11071 #11024
• Inference status now retries transient HTTP 429, 502, 503, and 504 responses up to three total attempts while preserving redacted output and the final unhealthy result. Nemotron 3 Super validation sends its required sampling and chat-template parameters, and the default Model Router pool replaces the retired Nemotron Nano route with GPT-OSS 20B High. #10956 #10910 #11070

Policy and integrations

• Deep Agents MCP status rejects symbolic links, dangling links, FIFOs, and other unsafe managed projection entries instead of treating them as ordinary adapter mismatches. Snapshot restore can rebuild the NemoClaw-owned projection with an atomic, no-follow replacement while preserving directory targets for explicit recovery. #10911 #10909
• Messaging and web-search setup verifies the exact checked-in OpenShell profile before registration or Ready reuse. Refreshing bridges retain their working credential until replacement minting succeeds, and named-gateway operations reject ambient endpoints that could redirect provider preparation. #10884 #10895
• Hermes Discord policy now grants network access only to the Hermes and Python runtime binaries used for Discord traffic. Reapplying the maintained preset removes the old generic Node.js grant without disturbing unrelated policy entries. #10682

Community thanks

• Thank you to @Dreamstick9 for documenting the correct gateway service unit and status command for each authority mode and install path. That clarification helps operators distinguish a broken gateway from a service-name mismatch. #10887

See every merged change in the full v0.0.119...v0.0.120 comparison.