docs: refresh 0.0.59 release notes#4790
Merged
Merged
Conversation
Contributor
📝 WalkthroughWalkthroughDocumentation updates for v0.0.59 align Ollama inference defaults across guides, expand NVIDIA Endpoints model options, clarify credential storage behavior for day-two operations, add v0.0.59 release notes, and adjust reference/frontmatter and contributor release-prep label wording. Changesv0.0.59 Release Documentation
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Contributor
|
🌿 Preview your docs: https://nvidia-preview-pr-4790.docs.buildwithfern.com/nemoclaw |
Contributor
E2E Advisor RecommendationRequired E2E: None Full advisor summaryE2E Recommendation AdvisorBase: Required E2E
Optional E2E
New E2E recommendations
|
Contributor
E2E Scenario Advisor RecommendationRequired scenario E2E: None Full scenario advisor summaryE2E Scenario AdvisorBase: Required scenario E2E
Optional scenario E2E
Relevant changed files
|
Contributor
PR Review AdvisorFindings: 0 needs attention, 1 worth checking, 0 nice ideas Review findings🛠️ Needs attention
🔎 Worth checking
🌱 Nice ideas
Consider writing more tests for
This is an automated advisory review. A human maintainer must make the final merge decision. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (7)
.agents/skills/nemoclaw-user-configure-inference/SKILL.md (1)
1-5:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the required SPDX license header to this Markdown file.
This file is missing the required SPDX header in Markdown-comment form.
As per coding guidelines: all
*.mdfiles must include SPDX headers, and Markdown files must use HTML comments.🤖 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 @.agents/skills/nemoclaw-user-configure-inference/SKILL.md around lines 1 - 5, Add the required SPDX license header as an HTML comment at the very top of the Markdown file (before the frontmatter) for the skill named "nemoclaw-user-configure-inference"; specifically insert a line like <!-- SPDX-License-Identifier: Apache-2.0 --> above the existing YAML frontmatter so the file meets the Markdown SPDX requirement.Source: Coding guidelines
.agents/skills/nemoclaw-user-configure-inference/references/inference-options.md (1)
1-3:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the required SPDX license header to this Markdown file.
This file is missing the required SPDX header in Markdown-comment form.
As per coding guidelines: all
*.mdfiles must include SPDX headers, and Markdown files must use HTML comments.🤖 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 @.agents/skills/nemoclaw-user-configure-inference/references/inference-options.md around lines 1 - 3, Add the required SPDX license header as an HTML comment at the very top of this Markdown file (above the "# NemoClaw Inference Options" heading and any imports), using the project's standard SPDX identifier format; ensure the header is an HTML comment so it remains a Markdown comment and matches the repo's SPDX style for *.md files.Source: Coding guidelines
docs/security/credential-storage.mdx (1)
2-3:⚠️ Potential issue | 🟠 Major | ⚡ Quick winUse Markdown HTML comments for SPDX header in this MDX file.
The SPDX lines are present, but the required Markdown format is HTML comments (not
#comment lines).As per coding guidelines, md/mdx files must include SPDX headers and “use HTML comments for Markdown.”
🤖 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/security/credential-storage.mdx` around lines 2 - 3, Replace the two plain-text SPDX lines with HTML-comment formatted SPDX headers so the mdx parser and our guidelines pick them up; specifically, locate the existing "SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved." and "SPDX-License-Identifier: Apache-2.0" lines in the docs/security/credential-storage.mdx content and wrap each as HTML comments (e.g., <!-- SPDX-FileCopyrightText: ... --> and <!-- SPDX-License-Identifier: ... -->), ensuring they remain the exact SPDX tokens.Source: Coding guidelines
.agents/skills/nemoclaw-user-configure-security/references/credential-storage.md (1)
1-3:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the required SPDX license header for Markdown files.
This Markdown file is missing the required SPDX header in Markdown comment format.
As per coding guidelines, files matching
**/*.{...md,mdx...}must include SPDX headers, using HTML comments for Markdown.🤖 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 @.agents/skills/nemoclaw-user-configure-security/references/credential-storage.md around lines 1 - 3, This Markdown file is missing the required SPDX header; add an HTML comment SPDX license header at the very top of the file (before the "# Credential Storage" heading and any imports) in the form <!-- SPDX-License-Identifier: <LICENSE> --> (for example <!-- SPDX-License-Identifier: MIT -->) so the file complies with the guideline that all .md/.mdx files include an SPDX header; locate the file content around the "# Credential Storage" heading and the import { AgentOnly } line to insert the header.Source: Coding guidelines
docs/about/release-notes.mdx (1)
2-3:⚠️ Potential issue | 🟠 Major | ⚡ Quick winSPDX comments should use HTML comment syntax in MDX files.
For Markdown/MDX, the SPDX header must be written as HTML comments rather than
#comments.🤖 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/about/release-notes.mdx` around lines 2 - 3, Replace the two SPDX lines that currently use Markdown '#' comments ("# SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved." and "# SPDX-License-Identifier: Apache-2.0") with HTML comment syntax so they become <!-- SPDX-FileCopyrightText: ... --> and <!-- SPDX-License-Identifier: Apache-2.0 --> at the top of the MDX file, preserving the exact SPDX text but using HTML comments instead of '#' markers.Source: Coding guidelines
.agents/skills/nemoclaw-user-overview/references/release-notes.md (1)
1-3:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the required SPDX header in Markdown comment format.
This Markdown file is missing the required SPDX license header (
<!-- ... -->) for*.mdfiles.🤖 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 @.agents/skills/nemoclaw-user-overview/references/release-notes.md around lines 1 - 3, Add the required SPDX license header as an HTML comment at the very top of the Markdown file: insert a single-line HTML comment like <!-- SPDX-License-Identifier: Apache-2.0 --> (or the project's required SPDX identifier) before the existing content so the file contains the required SPDX header in comment format; ensure there is a newline after the comment and that the original release notes text ("NVIDIA NemoClaw is available in early preview starting March 16, 2026.") remains unchanged.Source: Coding guidelines
.agents/skills/nemoclaw-user-reference/references/commands.md (1)
1-3:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the required Markdown SPDX header.
This
*.mdsource file should include the SPDX header using HTML comments at the top.🤖 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 @.agents/skills/nemoclaw-user-reference/references/commands.md around lines 1 - 3, Add an SPDX header as HTML comments at the very top of this Markdown file (above the "# NemoClaw CLI Commands Reference" title and the import line). Insert comments like an SPDX-FileCopyrightText line and an SPDX-License-Identifier line (e.g., <!-- SPDX-FileCopyrightText: YourOrg or Author --> and <!-- SPDX-License-Identifier: MIT -->) so the file contains the required SPDX header before any content.Source: Coding guidelines
🧹 Nitpick comments (1)
docs/about/release-notes.mdx (1)
20-24: ⚡ Quick winUse one sentence per line in the updated bullets.
Each bullet currently contains multiple sentences on one source line; split them so every sentence occupies its own line per docs style.
🤖 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/about/release-notes.mdx` around lines 20 - 24, Split each bullet so that each sentence is on its own line: for the bullet starting with "OpenClaw sandboxes..." break it into separate lines for the reconciliation, plugin registry refresh, path pinning, and approval compatibility sentences; for the "Inference setup..." bullet split into lines for model choices/first-start budgets, NVIDIA Endpoints Nemotron option, Local Ollama fallback, managed vLLM context window, and Local NVIDIA NIM startup behavior while keeping the reference link attached to the appropriate sentence; do the same for the "Hermes sandboxes..." bullet (routing and config sync), the "Credential and messaging boundaries..." bullet (rebuild/update reuse, channels add warning, and status reporting), and the "Sandbox startup..." bullet (healing permissions, CDI detection, probing legacy gateway, and argument validation), ensuring each sentence becomes its own bullet line and preserve the markdown links and original wording.Source: Coding guidelines
🤖 Prompt for all review comments with 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.
Inline comments:
In `@docs/inference/use-local-inference.mdx`:
- Around line 172-176: The bash code block includes a prompt marker "$$" before
the command; remove the prompt marker so the block is directly copyable. Edit
the snippet containing the environment variables NEMOCLAW_PROVIDER and
NEMOCLAW_MODEL and the command "nemoclaw onboard --non-interactive --yes" to
remove the "$$" prefix (i.e., leave the command on its own line) so the code
block contains only copyable CLI text.
---
Outside diff comments:
In
@.agents/skills/nemoclaw-user-configure-inference/references/inference-options.md:
- Around line 1-3: Add the required SPDX license header as an HTML comment at
the very top of this Markdown file (above the "# NemoClaw Inference Options"
heading and any imports), using the project's standard SPDX identifier format;
ensure the header is an HTML comment so it remains a Markdown comment and
matches the repo's SPDX style for *.md files.
In @.agents/skills/nemoclaw-user-configure-inference/SKILL.md:
- Around line 1-5: Add the required SPDX license header as an HTML comment at
the very top of the Markdown file (before the frontmatter) for the skill named
"nemoclaw-user-configure-inference"; specifically insert a line like <!--
SPDX-License-Identifier: Apache-2.0 --> above the existing YAML frontmatter so
the file meets the Markdown SPDX requirement.
In
@.agents/skills/nemoclaw-user-configure-security/references/credential-storage.md:
- Around line 1-3: This Markdown file is missing the required SPDX header; add
an HTML comment SPDX license header at the very top of the file (before the "#
Credential Storage" heading and any imports) in the form <!--
SPDX-License-Identifier: <LICENSE> --> (for example <!--
SPDX-License-Identifier: MIT -->) so the file complies with the guideline that
all .md/.mdx files include an SPDX header; locate the file content around the "#
Credential Storage" heading and the import { AgentOnly } line to insert the
header.
In @.agents/skills/nemoclaw-user-overview/references/release-notes.md:
- Around line 1-3: Add the required SPDX license header as an HTML comment at
the very top of the Markdown file: insert a single-line HTML comment like <!--
SPDX-License-Identifier: Apache-2.0 --> (or the project's required SPDX
identifier) before the existing content so the file contains the required SPDX
header in comment format; ensure there is a newline after the comment and that
the original release notes text ("NVIDIA NemoClaw is available in early preview
starting March 16, 2026.") remains unchanged.
In @.agents/skills/nemoclaw-user-reference/references/commands.md:
- Around line 1-3: Add an SPDX header as HTML comments at the very top of this
Markdown file (above the "# NemoClaw CLI Commands Reference" title and the
import line). Insert comments like an SPDX-FileCopyrightText line and an
SPDX-License-Identifier line (e.g., <!-- SPDX-FileCopyrightText: YourOrg or
Author --> and <!-- SPDX-License-Identifier: MIT -->) so the file contains the
required SPDX header before any content.
In `@docs/about/release-notes.mdx`:
- Around line 2-3: Replace the two SPDX lines that currently use Markdown '#'
comments ("# SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION &
AFFILIATES. All rights reserved." and "# SPDX-License-Identifier: Apache-2.0")
with HTML comment syntax so they become <!-- SPDX-FileCopyrightText: ... --> and
<!-- SPDX-License-Identifier: Apache-2.0 --> at the top of the MDX file,
preserving the exact SPDX text but using HTML comments instead of '#' markers.
In `@docs/security/credential-storage.mdx`:
- Around line 2-3: Replace the two plain-text SPDX lines with HTML-comment
formatted SPDX headers so the mdx parser and our guidelines pick them up;
specifically, locate the existing "SPDX-FileCopyrightText: Copyright (c) 2026
NVIDIA CORPORATION & AFFILIATES. All rights reserved." and
"SPDX-License-Identifier: Apache-2.0" lines in the
docs/security/credential-storage.mdx content and wrap each as HTML comments
(e.g., <!-- SPDX-FileCopyrightText: ... --> and <!-- SPDX-License-Identifier:
... -->), ensuring they remain the exact SPDX tokens.
---
Nitpick comments:
In `@docs/about/release-notes.mdx`:
- Around line 20-24: Split each bullet so that each sentence is on its own line:
for the bullet starting with "OpenClaw sandboxes..." break it into separate
lines for the reconciliation, plugin registry refresh, path pinning, and
approval compatibility sentences; for the "Inference setup..." bullet split into
lines for model choices/first-start budgets, NVIDIA Endpoints Nemotron option,
Local Ollama fallback, managed vLLM context window, and Local NVIDIA NIM startup
behavior while keeping the reference link attached to the appropriate sentence;
do the same for the "Hermes sandboxes..." bullet (routing and config sync), the
"Credential and messaging boundaries..." bullet (rebuild/update reuse, channels
add warning, and status reporting), and the "Sandbox startup..." bullet (healing
permissions, CDI detection, probing legacy gateway, and argument validation),
ensuring each sentence becomes its own bullet line and preserve the markdown
links and original wording.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: f8b18ff5-3864-47ac-b038-e8269896fff0
📒 Files selected for processing (8)
.agents/skills/nemoclaw-user-configure-inference/SKILL.md.agents/skills/nemoclaw-user-configure-inference/references/inference-options.md.agents/skills/nemoclaw-user-configure-security/references/credential-storage.md.agents/skills/nemoclaw-user-overview/references/release-notes.md.agents/skills/nemoclaw-user-reference/references/commands.mddocs/about/release-notes.mdxdocs/inference/use-local-inference.mdxdocs/security/credential-storage.mdx
miyoungc
added
area: docs
cv
approved these changes
Jun 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
$$nemoclawcommand placeholders.Verification
python3 scripts/docs-to-skills.py docs/ .agents/skills/ --prefix nemoclaw-user --doc-platform fern-mdxrg "permissive mode|shields down|shields up|shields status|config rotate-token|rotate-token" --glob '*.{md,mdx}'git diff --checknpm run docs(rerun outside sandbox after sandbox-onlytsxIPC permission failure)npm run typecheck:cliSource Summary
docs/about/release-notes.mdx,docs/reference/commands.mdx,docs/reference/troubleshooting.mdx: Summarize OpenClaw 2026.5.27 compatibility, runtime path pinning, plugin registry recovery, live gateway reconciliation, and clearer host-alias/startup diagnostics.docs/about/release-notes.mdx,docs/inference/inference-options.mdx,docs/inference/use-local-inference.mdx,docs/inference/switch-inference-providers.mdx: Document the release inference changes covering Local NIM waits, Hermes Anthropic routing, Nemotron 3 Ultra, the current Ollama starter fallback, and Spark managed-vLLM context length.docs/about/release-notes.mdx,docs/security/credential-storage.mdx,docs/manage-sandboxes/messaging-channels.mdx,docs/reference/troubleshooting.mdx: Capture permission healing, gateway-stored credential reuse, cross-sandbox messaging credential conflict checks, and CDI preflight diagnostics..agents/skills/nemoclaw-user-*: Regenerate the user skill references from the updated source docs..agents/skills/nemoclaw-contributor-update-docs/SKILL.md,.coderabbit.yaml: Add release-prep area labels for docs and skills PRs, and teach docs review guidance that$$nemoclawis the correct shared command placeholder for examples that work across agent aliases.Note: the
documentationlabel was not present in the repository, so this PR is labeled withv0.0.59only.Summary by CodeRabbit