NemoClaw v0.0.127 is out!!

[cjagwani]

NemoClaw v0.0.127 clarifies lifecycle authority across the stack. OpenClaw and Hermes now own their native gateways, plugins, packages, child processes, hooks, and background work. OpenShell continues to own sandbox containment and lifecycle, while NemoClaw selects the sandbox, projects credentials, observes health, and restores host-side access. Startup and deletion paths now wait for observable convergence before they report success.

Configuration and inference workflows now preserve more of the live environment. Export supports HTTP and HTTPS inference endpoints, managed vLLM settings, the selected Ollama model and digest, and complete read-only OpenClaw agent rosters. Shared-gateway route changes now explain their effect on other registered sandboxes. Docker authority, packaged gateway startup, and OpenShell SDK delivery also fail earlier when the selected host configuration cannot work.

This release also tightens credential and Model Context Protocol (MCP) boundaries, preserves messaging policy during sandbox reuse, and expands the documented Pi qualification and recovery contract. CI now retains better failure evidence, uses stable test owners, and removes live end-to-end (E2E) work that duplicated deterministic coverage.

Native agent and sandbox lifecycle

• #11792 returns gateway lifecycle authority to OpenClaw and Hermes. This removes duplicated supervision while keeping sandbox selection, credential projection, health observation, and host-forward repair in NemoClaw.
• #11906 delegates plugin, package, and supported self-update lifecycle to the native agent runtimes. Native state now survives restart, rebuild, and restore without NemoClaw rewriting valid agent configuration.
• #11698 records and verifies the complete managed-bootstrap handoff before retiring recovery state. Interrupted replacements therefore retain the information needed to recover safely.
• #11957 completes onboarding through one native-agent restart when initial setup leaves the gateway stopped. Retained E2E coverage now checks the new ownership boundary instead of expecting NemoClaw to respawn gateways.
• #11914, #11933, and #11950 wait for OpenClaw or Hermes gateway readiness after a sandbox starts. Transient startup observations no longer cause premature health or dashboard-forward failures.
• #11838 routes named sandbox deletion through one typed OpenShell lifecycle adapter. Destroy, rebuild, restore, and cleanup paths now share the same command, timeout, and failure classification.
• #11951 waits for OpenShell to report sandbox absence after an accepted deletion. A stale inventory read no longer causes a false failure, and uncertain results preserve local recovery state.
• #11614 verifies that the final sandbox is absent before removing its shared gateway. If cleanup cannot be proved, NemoClaw keeps the gateway and reports the reason.
• #11929 replays the provider-recorded Docker GPU selector during rebuild. An unsupported selector now stops the operation before the existing sandbox is deleted.
• #11733 gives Hermes Portable users a specific repair command for rejected executable permissions. Rollback diagnostics remain redacted and do not replace the original failure.

Configuration, inference, and host setup

• #11789 accepts HTTP and HTTPS inference endpoints during configuration export. This aligns export with endpoints that onboarding already accepts.
• #11889 preserves managed vLLM execution and model settings during export. Non-default timeout, token, and reasoning settings no longer invalidate an otherwise verified profile.
• #11891 exports the selected Ollama model with its verified SHA-256 digest. Exports no longer substitute the default model when another installed model is active.
• #11900 exports every supported read-only OpenClaw agent in runtime order. The complete document is rejected if any roster member conflicts with the verified primary inference route.
• #11947 permits provider-only or model-only changes on a shared OpenShell gateway. NemoClaw warns which registered sandboxes the route change affects and still rejects endpoint, credential, API-family, and incomplete-route conflicts.
• #11786 treats DOCKER_CONTEXT as the operator-selected Docker authority. Readiness and onboarding no longer certify a fallback daemon when the selected context is unreachable.
• #11843 writes the complete authenticated gateway environment before restarting an upgraded packaged service. The service now binds the port that onboarding expects.
• #11921 delivers and verifies the required OpenShell SDK without GitHub credentials. Installation and contributor setup now stop when the SDK cannot load instead of leaving commands partially functional.

Credentials, MCP, and messaging

• #11702 avoids repeated URL-scheme scans in long diagnostics while preserving credential redaction. Large non-URL messages no longer make credential-safe diagnostics take seconds to process.
• #11865 rejects an untrusted OPENSHELL_GATEWAY_ENDPOINT override before any host-side probe or provider mutation. The diagnostic identifies the setting without exposing its value.
• #11405 preserves a recorded trusted private host during MCP tool discovery and credential probes. Servers without recorded trust keep the strict public-address boundary.
• #11866 documents that managed MCP egress applies to the selected agent adapter. It directs operators to the bounded mcp status probe instead of treating an interactive curl denial as a broken managed route.
• #10782 preserves an active messaging channel and its network policy during sandbox reuse when durable credential bindings still prove the configuration. Explicit channel or credential removal still disables the channel.
• #11829 downloads the OpenClaw gateway token through the typed sandbox-transfer adapter. Failed or interrupted transfers keep the existing token-free fallback and cleanup order.

Pi, workspaces, and documentation

• #10355 preserves recorded Pi context-window, output-token, and reasoning settings across rebuild. The gated Pi qualification path now checks context-free automation and interactive session persistence across onboarding, rebuild, and recovery.
• #11524 adds TOOLS.md and HEARTBEAT.md to the documented OpenClaw state-transfer procedure. It also identifies generated POLICY.md as state that must not be uploaded from a backup.
• #11908 removes hidden experimental-profile guidance from public documentation. Readers no longer see an internal profile presented as a supported surface.
• #11907 documents the required Podman 5.7.0 client and local engine for Hermes Portable. #11926 restores the complete Hermes quickstart and Ollama page structure around that guidance.
• #12003 adds the canonical dated release entry and connects each release theme to its owning documentation.

CI and release confidence

• #11930 lets pull-request CI reuse a reviewed OpenShell SDK archive from the main workflow. Bot-generated commits no longer depend on a separate event that GitHub can suppress.
• #11925 retains Advisor failure artifacts before cleanup, and #11935 validates coordinator evidence before reporting a shadow decision. Failed or malformed reviews remain fail-closed.
• #11931 requires contributor and maintainer workflows to choose the shortest stable test owner. Live E2E remains focused on behavior that requires a real runtime boundary.
• #11948 removes assertions for the retired Shields migration path. #11969 removes redundant authentication and inference targets while retaining their observable and security outcomes elsewhere.
• #11912 lets selected live E2E cleanup paths distinguish an absent gateway from an observation failure. Fresh runners can proceed without weakening terminal cleanup checks.
• #11964 validates Pi qualification receipt parity against the staged tree during a local merge. Qualified image-input changes already on the target branch no longer block an otherwise valid merge.
• #11987 repairs Hermes startup, OpenClaw distribution auditing, and the offline wheel-test budget after native lifecycle changes. The checks now match the shipped agent images and migration behavior.
• #11980 keeps the required growth-guardrail check visible while skipping main-only tooling for pull requests that target another branch.