Skip to content

docs(changelog): prepare v0.0.105 release notes #8576

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jyaunches merged 2 commits into from
Aug 7, 2026
Merged

docs(changelog): prepare v0.0.105 release notes #8576

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e33117a
docs(changelog): prepare v0.0.105 release notes
jyaunches Aug 7, 2026
6d3e816
docs(changelog): honor release skip policy
jyaunches Aug 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
41 changes: 41 additions & 0 deletions docs/changelog/2026-08-07.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,41 @@
{/*
* SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
* SPDX-License-Identifier: Apache-2.0
*/}
Comment on lines +1 to +4

@coderabbitai coderabbitai Bot Aug 7, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win

Use an HTML comment for the SPDX header.

Line 1-4 uses a JSX comment. The applicable guideline requires HTML comments for Markdown-style files. Replace the wrapper before release.

Proposed fix 
-{/*
- * SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
- * SPDX-License-Identifier: Apache-2.0
- */}
+<!--
+SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
+SPDX-License-Identifier: Apache-2.0
+-->
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
{/*
* SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
* SPDX-License-Identifier: Apache-2.0
*/}
<!--
SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
SPDX-License-Identifier: Apache-2.0
-->
🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/changelog/2026-08-07.mdx` around lines 1 - 4, Replace the JSX comment
wrapper around the SPDX header in the changelog file with an HTML comment
wrapper, preserving the existing copyright and license text unchanged.

Source: Coding guidelines


## v0.0.105

NemoClaw v0.0.105 upgrades the managed OpenShell runtime to v0.0.99 and adds its sandbox-name, credential, policy, and migration contracts.
It 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, and agent output integrity.

- The managed OpenShell runtime now uses v0.0.99 across installation, gateways, sandboxes, supervisors, and managed agent images.
NemoClaw enforces the new routable sandbox-name contract before destructive upgrade work, updates managed MCP and network-policy behavior, and retries a cold empty glibc probe only after it confirms cleanup of the first probe container.
For more information, refer to [Update Sandboxes](/user-guide/openclaw/manage-sandboxes/operate-sandboxes/update-sandboxes), [Configure Runtime Identity](/user-guide/openclaw/reference/configure-runtime-identity), and [Troubleshooting](/user-guide/openclaw/reference/troubleshooting).
- 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](/user-guide/openclaw/inference/validate-inference/understand-provider-validation), [Use Ollama](/user-guide/openclaw/inference/local-inference/set-up-ollama), and [Additional Setup for Windows Machines](/user-guide/openclaw/get-started/additional-setup/windows-preparation).
- 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](/user-guide/openclaw/inference/local-inference/set-up-vllm), [Set Up vLLM on Two DGX Sparks](/user-guide/openclaw/inference/local-inference/set-up-vllm-on-two-dgx-sparks), and [Troubleshooting](/user-guide/openclaw/reference/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](/user-guide/openclaw/manage-sandboxes/configure-sandboxes/understand-runtime-changes), [Recover and Rebuild Sandboxes](/user-guide/openclaw/manage-sandboxes/operate-sandboxes/recover-and-rebuild-sandboxes), and [Security Best Practices](/user-guide/openclaw/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](/user-guide/openclaw/manage-sandboxes/operate-sandboxes/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](/user-guide/hermes/reference/commands) and [Troubleshooting](/user-guide/hermes/reference/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](/user-guide/openclaw/reference/network-policies) and the [NemoClaw CLI Commands Reference](/user-guide/openclaw/reference/commands).
- 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](/user-guide/openclaw/deployment/deploy-to-headless-server) and the [NemoClaw CLI Commands Reference](/user-guide/openclaw/reference/commands).
- 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.
Comment on lines +37 to +38

@coderabbitai coderabbitai Bot Aug 7, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Add a documentation link for OpenClaw output reconciliation.

Line 37-38 describes a user-visible output contract but has no For more information reference. Add the current Fern-published documentation route for this behavior to satisfy the release-note objective.

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/changelog/2026-08-07.mdx` around lines 37 - 38, Add a “For more
information” link to the OpenClaw message-handling release-note entry describing
cumulative assistant snapshot reconciliation, using the current Fern-published
documentation route for this behavior and preserving the existing release-note
text.

- 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](/user-guide/deepagents/reference/commands) and [Run LangChain Deep Agents Code](/user-guide/deepagents/manage-sandboxes/operate-sandboxes/run-deep-agents-code).
Loading