Skip to content

docs: add v0.0.100 release entry #8030

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
senthilr-nv merged 1 commit into from
Aug 1, 2026
Merged

docs: add v0.0.100 release entry #8030

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
47 changes: 47 additions & 0 deletions docs/changelog/2026-07-31.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,47 @@
{/*
* 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 1, 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.

This MDX file uses a JSX comment, but the repository requires HTML comments for SPDX headers in Markdown and MDX files. Replace lines 1-4 with an HTML comment.

As per coding guidelines, every source file must include the appropriate SPDX header, and Markdown and MDX files must use HTML comments for SPDX headers.

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-07-31.mdx` around lines 1 - 4, Replace the JSX comment
wrapping the SPDX header at the beginning of the MDX file with an HTML comment,
preserving the existing copyright and license text exactly.

Source: Coding guidelines


## v0.0.100

NemoClaw v0.0.100 strengthens restored OpenClaw pairing, transactional sandbox replacement, managed Deep Agents Code, and host readiness provenance.
It also improves onboarding recovery, lifecycle cleanup, Hermes image builds, runtime diagnostics, documentation, and trusted end-to-end (E2E) evidence.

- OpenClaw cross-sandbox restore now uses descriptor-pinned clone pairing, while fresh onboarding continues to use generated pairing identity.
A restored clone can perform one bounded scope-upgrade recovery and tolerate a brief pending-request publication interval.
Unsafe filesystem shapes, persistent malformed state, and mismatched identities still fail closed.
For more information, refer to [Create and Restore Snapshots](/user-guide/openclaw/manage-sandboxes/state-and-backups/create-and-restore-snapshots).
- Managed Model Context Protocol (MCP) startup for Deep Agents Code now works when OpenShell seccomp denies `memfd_create` and workspace-backed `/tmp` rejects `O_TMPFILE`.
The Deep Agents Code sandbox receives a 1 MiB private tmpfs with verified mount options, and the managed runtime keeps its anonymous descriptor and integrity checks.
For more information, refer to [Run LangChain Deep Agents Code](/user-guide/deepagents/manage-sandboxes/operate-sandboxes/run-deep-agents-code).
- Managed Deep Agents Code requests now apply the recorded compatible-endpoint reasoning effort at runtime.
Recovered onboarding and sandbox recreation also preserve recorded reasoning mode and effort instead of accepting unrelated ambient values.
For more information, refer to [Quickstart with Deep Agents](/user-guide/deepagents/get-started/quickstart) and [Configure Model Capabilities](/user-guide/openclaw/inference/manage-inference/configure-model-capabilities).
- `rebuild` and same-name onboarding replacement now record a transaction before the first destructive mutation.
Recovery binds the source, replacement, registry generation, and OpenShell gateway, then continues the recorded operation or fails closed when those identities drift.
For more information, refer to [Recover and Rebuild Sandboxes](/user-guide/openclaw/manage-sandboxes/operate-sandboxes/recover-and-rebuild-sandboxes) and the [NemoClaw CLI Commands Reference](/user-guide/openclaw/reference/commands).
- Compatible-endpoint onboarding now limits the Responses API streaming-event probe to 12 seconds while preserving the Chat Completions API fallback.
Host interruptions during an active onboarding step produce the existing resumable recovery path instead of an invalid state transition.
DGX Station Express also preserves its owner-only resume receipt when automatic dual-Station discovery selects the single-Station fallback.
For more information, refer to [Choose a Compatible Inference API](/user-guide/openclaw/inference/custom-endpoints/choose-compatible-inference-api), [Quickstart](/user-guide/openclaw/get-started/quickstart), and [Prepare DGX Station to Install NemoClaw](/user-guide/openclaw/get-started/additional-setup/dgx-station-preparation).
- `nemoclaw status` now reads terminal-runtime out-of-memory counters through a bounded host-side Docker probe, so a recorded kill produces degraded status and rebuild guidance.
Destroying the final sandbox now stops a packaged OpenShell gateway service and refuses cleanup when the service remains active.
For more information, refer to the [NemoClaw CLI Commands Reference](/user-guide/openclaw/reference/commands) and [Troubleshooting](/user-guide/openclaw/reference/troubleshooting).
- `shields down` now succeeds without changing state when an OpenClaw configuration already has the exact mutable posture.
Cloudflare Tunnel cleanup verifies that the recorded process still belongs to `cloudflared` before each signal and removes a stale PID file without signaling an unrelated process.
For more information, refer to [Understand Runtime Changes](/user-guide/openclaw/manage-sandboxes/configure-sandboxes/understand-runtime-changes) and [Run Sandboxes](/user-guide/openclaw/manage-sandboxes/operate-sandboxes/run-sandboxes).
- Managed Hermes image probes now run through a checked-in Python runner, so OpenShell gateways that use Docker's legacy builder enforce the same image assertions as BuildKit.
For more information, refer to [Install Hermes Plugins](/user-guide/hermes/manage-sandboxes/install-hermes-plugins).
- `nemoclaw host probe` schema `1.1.0` now identifies the exact compiled CLI version and immutable source revision for every readiness result.
Consumers can reject stale or mismatched readiness producers before they use host evidence.
For more information, refer to [System Readiness](/user-guide/openclaw/reference/system-readiness).
- Provider-neutral runtime bundles now enforce provider, workload, ownership, and registry contracts for the existing Docker and Kubernetes paths.
Root-owned managed shared-state transactions enforce atomic application and rollback contracts but remain inactive in production onboarding.
Neither foundation activates a new runtime provider or adds a CLI, configuration, default, or support claim.
- Documentation now includes a focused Deep Agents Code operation page, publishes the agentic-documentation guide in every guide variant, and uses host capability detection for optional NVIDIA DORI routing.
It also adds missing recovery, memory-search, and two-DGX Station verification guidance identified by post-tag documentation audits.
For more information, refer to [Run LangChain Deep Agents Code](/user-guide/deepagents/manage-sandboxes/operate-sandboxes/run-deep-agents-code) and [Engineer Documentation for AI Agents](/user-guide/openclaw/resources/engineer-agentic-documentation).
- Trusted E2E now binds request proofs to explicit authenticated phases, keeps calibration ancestry durable after evidence-source PR refs disappear, and validates coupled MCP credential evidence.
Recovery repetition moved into deterministic integration tests, while the retained live test verifies one exact replacement process and connect-driven recovery.
The PR Review Advisor now preserves validated second-opinion lane disagreements and rejects malformed E2E collections.
Loading