v0.0.71

NemoClaw v0.0.71 improves gateway recovery, OpenShell gateway authentication, policy provenance, uninstall safety, Windows bootstrap diagnostics, messaging behavior, and inference guidance.

  • Gateway lifecycle operations use a host-mediated control path for built-in OpenClaw and Hermes sandboxes. recover and gateway restart target the supervised gateway through the supported topology controller, re-check forwards after replacement, preserve explicit runtime model overrides during OpenClaw reconciliation, and write guard-chain recovery warnings into the gateway log for crash-loop diagnosis. For more information, refer to Recover and Rebuild Sandboxes, NemoClaw CLI Commands Reference, Troubleshooting, and Trusted Computing Base.
  • OpenShell 0.0.71 is the validated gateway release for this train. NemoClaw generates local TLS, mTLS, and sandbox JWT material for Docker-driver gateways, keeps gateway binds on loopback while JWT auth is active, and documents the explicit compatibility-container boundary for older trusted Linux hosts. For more information, refer to OpenShell 0.0.71 Review, Security Best Practices, and Troubleshooting.
  • Network policy output now explains why active presets are present. policy-list annotates verified active presets with tier, agent, user-added, or source-unverified provenance; Restricted onboarding suppresses agent-required preset additions; the Balanced tier no longer includes weather; and the weather preset covers read-only wttr.in lookups when you add it explicitly. For more information, refer to Network Policies, NemoClaw CLI Commands Reference, and Common NemoClaw Integration Policy Examples.
  • Day-two maintenance paths are more explicit. nemoclaw uninstall --destroy-user-data provides a visible full-purge flag while keeping --yes non-destructive for preserved user data, custom Dockerfile onboarding documents cold and warm build-cache behavior, and host-side OpenClaw agent dispatch warns on stderr when a recent shields auto-relock may explain a failed one-shot command. For more information, refer to Recover and Rebuild Sandboxes and NemoClaw CLI Commands Reference.
  • Messaging and inference setup have clearer runtime defaults and selection guidance. Microsoft Teams channel setup uses final-message delivery by default and runtime mention hints, non-interactive Ollama setup refuses unsafe loopback rewrites when sudo evidence is unavailable, compatible local endpoint docs explain the default chat-completions path, and the inference guide adds model task-fit and capability-audit guidance. For more information, refer to Choose Messaging Channels, Choose a Local Inference Server, Choose an Inference Provider, and Audit Model Capabilities.
  • Windows setup output is safer to share during troubleshooting. The Windows bootstrap redacts PowerShell transcript metadata and temporary paths from WSL install output, and it asks for a reboot only when WSL reports one is required. For more information, refer to Prepare Windows for NemoClaw and Troubleshooting.