Release Notes

v0.0.105

NemoClaw v0.0.105 restores local and managed inference paths across Windows, Linux ARM64, DGX Spark, Ollama, vLLM, and managed llama.cpp. It also improves Shields recovery, uninstall ownership, Hermes operations, network-policy feedback, remote dashboard guidance, agent output integrity, and cold container compatibility probing.

• Strict local-provider validation now retries one reasoning-only tool-call truncation with a larger token budget and still fails unless the retry returns a structured tool call. vLLM parser errors now identify the required automatic tool-choice and parser settings, while Windows-host Ollama readiness runs from the Docker Desktop network context that reaches host.docker.internal. For more information, refer to Understand Provider Validation, Use Ollama, and Additional Setup for Windows Machines.
• Managed vLLM onboarding now accepts its authenticated loopback endpoint without requiring an unrelated trusted-private capability. Dual DGX Spark discovery accepts the filtered ip neighbor output produced by the host and names the failed rail check, while eligible native Linux ARM64 hosts can prove denylisted GPU names with the bounded Docker CUDA workload. The experimental managed llama.cpp lifecycle also uses the exact loopback port declared by its selected recipe. For more information, refer to Set Up vLLM, Set Up vLLM on Two DGX Sparks, and Troubleshooting.
• Shields down can now recover an OpenClaw sandbox whose protected startup failed before readiness, but only after the installed guard proves that no startup child or readiness lease remains. Hermes Shields transitions now wait for the trusted inference route to converge and roll back the existing transaction when the bounded route check fails. For more information, refer to Understand Runtime Changes, Recover and Rebuild Sandboxes, and Security Best Practices.
• Full uninstall no longer matches unrelated Docker containers and images whose names contain openclaw. It leaves resources from a separate OpenClaw installation in place while continuing to remove the Docker resources that NemoClaw identifies as its own. For more information, refer to Uninstall NemoClaw.
• Hermes now keeps legacy dashboard startup inside its prepared, privilege-separated profile and avoids unintended re-execution into the machine-level dashboard. The nemohermes <sandbox> sessions delete <id> command also uses in-memory SQLite temporary storage so session deletion works inside the restricted sandbox process context. For more information, refer to the NemoClaw CLI Commands Reference and Troubleshooting.
• An interactive policy restore refusal now reports Cancelled., and a non-interactive refusal prints the complete usage line. Both refusal paths stop before policy mutation. For more information, refer to Network Policies Reference and the NemoClaw CLI Commands Reference.
• When an SSH operator needs a port forward for a running OpenClaw or Hermes dashboard, status now points to the tokenized URL from dashboard-url. The hint remains absent for non-SSH sessions, stopped gateways, routable dashboards, and Deep Agents Code sandboxes. For more information, refer to Deploy to a Headless Server and the NemoClaw CLI Commands Reference.
• OpenClaw message handling now reconciles cumulative assistant snapshots with delta and replacement events before it publishes the final response. This recovers text from later snapshots without duplicating earlier output and uses the pinned headless loopback client identity accepted by OpenClaw v2026.7.1.
• Managed Deep Agents Code requests for the reviewed Nemotron Ultra model IDs now include the fixed nonempty-content template argument without trusting mutable provider parameters. A successful Deep Agents Code skill installation also prints its confirmed SHA-256 content digest so operators can compare later installations. For more information, refer to the NemoClaw CLI Commands Reference and Run LangChain Deep Agents Code.