Release Notes

July 12, 2026

v0.0.81

NemoClaw v0.0.81 strengthens rebuild and snapshot state preservation, repairs local compatible inference and WhatsApp setup, improves Docker restart recovery, and makes onboarding, backup, and security diagnostics easier to act on.

  • Rebuild and restore preserve more user-owned state without letting old backups replace current managed configuration. Agent manifests can declare key-level restore ownership, managed Deep Agents restores keep only allowlisted UI and thread preferences, and Hermes rebuilds retain the Web Dashboard profile under /sandbox/.hermes/dashboard-home/, including its MEMORY.md and USER.md files. Deep Agents snapshot creation also falls back to /proc when ps is unavailable while continuing to fail closed when it cannot prove the runtime is idle. For more information, refer to Create and Restore Snapshots and Understand Sandbox State.
  • Compatible inference setup handles more endpoint and model contracts automatically. Eligible loopback endpoints on ports 8000, 11434, and 11435 are validated on the host and registered through host.openshell.internal, GPT-5 and the o1, o3, and o4 model families use max_completion_tokens, and related provider validation probes can reuse bounded HTTPS connections with established fallbacks. Direct blueprint apply now aborts without persisting an incomplete plan or reporting false completion when provider creation or inference configuration fails. For more information, refer to Set Up an OpenAI-Compatible Endpoint and Choose a Compatible Inference API.
  • Sandbox lifecycle recovery covers more host restart and teardown cases. On supported local Docker deployments, recover can transactionally replace a legacy keepalive container whose managed supervisor disappeared after a restart, and it commits only after health and settle checks pass. Hermes persists its managed startup command across direct Docker restarts, while unattended destruction of the final sandbox releases the shared gateway by default on macOS. For more information, refer to Recover and Rebuild Sandboxes, NemoClaw CLI Commands Reference, and Troubleshooting.
  • Managed Deep Agents sessions skip optional first-run setup and clean up their own process trees on disconnect. The image includes ripgrep, pre-completes optional upstream onboarding, suppresses the optional Tavily warning unless web search is configured or used, and refuses a managed fetch CA bundle with unsafe ownership, permissions, links, or content. For more information, refer to Quickstart with LangChain Deep Agents Code and Security Best Practices.
  • WhatsApp pairing now uses the OpenClaw loopback gateway so a successful QR login can start the channel without moving a gateway token or requiring operator.admin. Externally installed channel plugins now retain verified npm provenance, which enables the trusted persistent-state features expected by current OpenClaw releases. For more information, refer to Set Up WhatsApp.
  • Backup and onboarding failures provide more specific recovery evidence. backup-all tells you to start a stopped sandbox or container and rerun the backup or installer, and backup failures identify these causes when available: permission denied, tar read error, or absent after extraction. A created-but-not-ready sandbox prints a lifecycle receipt with its readiness gate, timeout, and cleanup result, onboarding progress waits while an interactive prompt owns the terminal, and resumed onboarding does not advance durable state from stale replay results. For more information, refer to Create and Restore Snapshots, NemoClaw Quickstart, NemoClaw CLI Commands Reference, and Troubleshooting.
  • Security and policy diagnostics preserve more context without hiding risk. OpenClaw security audits keep NemoClaw-managed dashboard compatibility findings visible with their severity, remediation, and recorded reason, while token-shaped URL query values are redacted even when their parameter names look benign. The custom Streamable HTTP MCP policy recipe also scopes DELETE to the exact MCP endpoint used for session termination. For more information, refer to Security Best Practices and Customize the Network Policy.