docs: refresh v0.0.60 release notes#4879
Merged
Merged
Conversation
miyoungc
added
v0.0.60
Contributor
|
Linter diff in the way? Review this PR in Change Stack to focus on meaningful changes and expand context only when needed. 📝 WalkthroughWalkthroughThis PR updates NemoClaw documentation for v0.0.60, covering runtime context guidance, policy tier defaults, Hermes dashboard workflows, managed inference setup, command reference accuracy, and lifecycle/security clarifications across agent skills and public docs. Changesv0.0.60 documentation refresh across OpenClaw and Hermes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
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, 4 worth checking, 0 nice ideas Review findings🛠️ Needs attention
🔎 Worth checking
🌱 Nice ideas
Consider writing more tests for
Since last review detailsCurrent findings:
This is an automated advisory review. A human maintainer must make the final merge decision. |
Contributor
|
🌿 Preview your docs: https://nvidia-preview-pr-4879.docs.buildwithfern.com/nemoclaw |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Note
Due to the large number of review comments, Critical severity comments were prioritized as inline comments.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (26)
skills/nemoclaw-user-configure-security/SKILL.md (1)
1-6:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the required SPDX header to this Markdown file.
This file is missing the mandated Markdown SPDX header comment block.
🤖 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 `@skills/nemoclaw-user-configure-security/SKILL.md` around lines 1 - 6, The SKILL.md for "nemoclaw-user-configure-security" is missing the required SPDX header; add the SPDX license identifier comment block at the top of SKILL.md (matching the declared license "Apache-2.0") so the file includes the mandated SPDX header comment; update the header immediately above the existing YAML frontmatter to ensure automated tooling recognizes the SPDX metadata for this skill.Source: Coding guidelines
skills/nemoclaw-user-manage-policy/references/approve-network-requests.md (1)
1-3:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRestore the required SPDX header in this Markdown file.
This file does not include the required SPDX Markdown header comment.
🤖 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 `@skills/nemoclaw-user-manage-policy/references/approve-network-requests.md` around lines 1 - 3, Add the required SPDX Markdown header comment to the top of this document (above the "# Approve or Deny Agent Network Requests" heading): restore the SPDX-FileCopyrightText and SPDX-License-Identifier comment lines so the file contains the project's standard SPDX header in Markdown comment form.Source: Coding guidelines
skills/nemoclaw-user-manage-policy/SKILL.md (1)
1-6:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the required SPDX header to this Markdown file.
The required SPDX header comment is missing from this file.
🤖 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 `@skills/nemoclaw-user-manage-policy/SKILL.md` around lines 1 - 6, Add the required SPDX header as an HTML comment at the very top of the Markdown file (before the YAML frontmatter) to match the existing license field; e.g. add <!-- SPDX-License-Identifier: Apache-2.0 --> as the first line so the declared license ("license: \"Apache-2.0\"") in the frontmatter aligns with the SPDX header and is discoverable by tooling; ensure you place it before the 'name', 'description', and 'license' fields.Source: Coding guidelines
skills/nemoclaw-user-monitor-sandbox/SKILL.md (1)
1-16:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the SPDX header (HTML comments) after the frontmatter block.
This Markdown file is missing the required SPDX license header.
🤖 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 `@skills/nemoclaw-user-monitor-sandbox/SKILL.md` around lines 1 - 16, Add the required SPDX license header as an HTML comment immediately after the frontmatter block in SKILL.md: insert a line like <!-- SPDX-License-Identifier: Apache-2.0 --> right after the closing --- that ends the YAML frontmatter (use the license field value "Apache-2.0" from the frontmatter), ensuring the header appears before the rest of the Markdown content (e.g., before "Monitor Sandbox Activity and Debug Issues").Source: Coding guidelines
.agents/skills/nemoclaw-user-reference/references/troubleshooting.md (2)
1-1593:⚠️ Potential issue | 🟠 Major | ⚡ Quick winDo not edit autogenerated
.agents/skills/nemoclaw-user-*files directly.This path is explicitly marked as autogenerated and should be regenerated from source docs/skills instead of hand-editing.
🤖 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/troubleshooting.md around lines 1 - 1593, The file header warns that `.agents/skills/nemoclaw-user-*` files are autogenerated and must not be edited directly; revert any manual edits to ".agents/skills/nemoclaw-user-reference/references/troubleshooting.md" and regenerate it from the canonical source (docs/skills) so the autogenerated artifact matches the source-of-truth; use the repository's documentation build or skill-generation script that produces the nemoclaw-user-reference outputs and confirm the regenerated troubleshooting.md includes the original autogenerated warning line.Source: Coding guidelines
1-5:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the required SPDX license header in Markdown-comment format.
The required SPDX header is missing from this Markdown file.
🤖 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/troubleshooting.md around lines 1 - 5, Add the required SPDX license header as a Markdown HTML comment at the very top of the file (before the "# Troubleshooting" heading); use the project's standard SPDX identifier format (SPDX-License-Identifier: <LICENSE>) so the header is discoverable by tooling and matches other docs in the repo.Source: Coding guidelines
skills/nemoclaw-user-reference/references/troubleshooting.md (1)
1-5:⚠️ Potential issue | 🟠 Major | ⚡ Quick winInsert the required SPDX license header at the top of this file.
The mandatory Markdown SPDX header comments are missing.
🤖 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 `@skills/nemoclaw-user-reference/references/troubleshooting.md` around lines 1 - 5, Add the mandatory SPDX license header as a Markdown/HTML comment block at the very top of this file (above the "# Troubleshooting" title); include an SPDX-License-Identifier line and an SPDX-FileCopyrightText line with the correct year and copyright holder for this project so the file meets the repository's licensing header requirements.Source: Coding guidelines
skills/nemoclaw-user-agent-skills/SKILL.md (1)
1-6:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the mandated SPDX header for Markdown files.
This file is missing the required Markdown SPDX 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 `@skills/nemoclaw-user-agent-skills/SKILL.md` around lines 1 - 6, The SKILL.md file for "nemoclaw-user-agent-skills" is missing the mandated SPDX license HTML comment; add the SPDX identifier as an HTML comment at the very top of the Markdown file (e.g., the SPDX-License-Identifier matching the existing license field "Apache-2.0") so the file begins with the required SPDX header comment before the YAML frontmatter.Source: Coding guidelines
skills/nemoclaw-user-get-started/references/quickstart-hermes.md (1)
1-1:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the required SPDX header for Markdown files.
The file is missing the required SPDX HTML comment header before the document content.
🤖 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 `@skills/nemoclaw-user-get-started/references/quickstart-hermes.md` at line 1, Add the required SPDX HTML comment header at the top of the Markdown file before the document content; insert a single-line HTML comment like <!-- SPDX-FileCopyrightText: <owner> --> followed by <!-- SPDX-License-Identifier: <license-id> --> (replace <owner> and <license-id> appropriately) immediately above the existing "# NemoClaw Quickstart with Hermes" heading so the file includes the mandatory SPDX header.Source: Coding guidelines
skills/nemoclaw-user-reference/SKILL.md (1)
1-5:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the required SPDX header for Markdown files.
Line 1 starts frontmatter without the required SPDX HTML comment header for
.mdsources.🤖 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 `@skills/nemoclaw-user-reference/SKILL.md` around lines 1 - 5, The Markdown file SKILL.md is missing the required SPDX HTML comment header; add an SPDX license identifier comment (e.g. <!-- SPDX-License-Identifier: Apache-2.0 -->) immediately before the existing YAML frontmatter at the top of SKILL.md so the SPDX header precedes the document frontmatter and matches the declared license.Source: Coding guidelines
.agents/skills/nemoclaw-user-get-started/references/quickstart-hermes.md (1)
1-1:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the required SPDX header for Markdown files.
This Markdown file does not include the mandatory SPDX HTML comment header.
🤖 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-get-started/references/quickstart-hermes.md at line 1, Add the required SPDX HTML comment header at the top of the Markdown file that currently starts with the heading "# NemoClaw Quickstart with Hermes"; insert the standard SPDX header (an HTML comment like <!-- SPDX-FileCopyrightText: ... and SPDX-License-Identifier: ... -->) immediately above that heading so the file includes the mandatory SPDX metadata.Source: Coding guidelines
skills/nemoclaw-user-get-started/SKILL.md (1)
1-6:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the required SPDX header for Markdown files.
This
.mdfile is missing the required SPDX HTML comment header before content/frontmatter.🤖 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 `@skills/nemoclaw-user-get-started/SKILL.md` around lines 1 - 6, This Markdown file (SKILL.md) is missing the required SPDX HTML comment header; add the SPDX header (e.g., <!-- SPDX-License-Identifier: Apache-2.0 -->) immediately before the YAML frontmatter start ('---') at the top of the file so the license identifier is present as an HTML comment while keeping the existing frontmatter and fields (name, description, license) intact.Source: Coding guidelines
.agents/skills/nemoclaw-user-get-started/SKILL.md (1)
1-5:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the required SPDX header for Markdown files.
This autogenerated
.mdfile still needs the repository-required SPDX HTML comment header at the top.
Based on learnings:.agents/skills/nemoclaw-user-*/*.mdchanges are expected when correspondingdocs/sources change; avoid flagging them as manual edits.🤖 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-get-started/SKILL.md around lines 1 - 5, The file lacks the repository-required SPDX HTML comment header at the top of the Markdown; add the standard SPDX header comment (e.g. <!-- SPDX-License-Identifier: Apache-2.0 -->) as the very first line of .agents/skills/nemoclaw-user-get-started/SKILL.md so the file contains the required SPDX metadata while leaving the existing YAML fields (name: "nemoclaw-user-get-started", description, license) unchanged; ensure the header is an HTML comment (not part of the YAML frontmatter) and saved so autogenerated docs tooling recognizes it.Sources: Coding guidelines, Learnings
skills/nemoclaw-user-deploy-remote/references/brev-web-ui.md (1)
1-1:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRestore the required SPDX header at the top of this Markdown file.
This file is missing the mandatory SPDX copyright and license header in Markdown comment form.
As per coding guidelines: “All source files must include an SPDX license header … (use HTML comments for Markdown).”Suggested patch
+<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. --> +<!-- SPDX-License-Identifier: Apache-2.0 --> + # Launch NemoClaw with the Brev Web UI🤖 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 `@skills/nemoclaw-user-deploy-remote/references/brev-web-ui.md` at line 1, This Markdown file is missing the mandatory SPDX header; add the required SPDX copyright and license header as an HTML comment at the very top of the file (above the existing "# Launch NemoClaw with the Brev Web UI" heading). Ensure the comment includes the copyright line and the SPDX-License-Identifier (e.g., "SPDX-FileCopyrightText: <copyright holder>" and "SPDX-License-Identifier: <license>") formatted according to project guidelines.Source: Coding guidelines
skills/nemoclaw-user-reference/references/architecture.md (1)
1-4:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the mandatory SPDX header.
The required Markdown SPDX header is missing from this file.
As per coding guidelines, “All source files must include an SPDX license header … (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 `@skills/nemoclaw-user-reference/references/architecture.md` around lines 1 - 4, Add the required SPDX license header as an HTML comment at the top of the Markdown file that currently starts with the heading "Architecture Details"; insert a single-line or multi-line HTML comment containing the SPDX identifier (e.g., <!-- SPDX-License-Identifier: MIT -->) before the existing content so the file (references/architecture.md) includes the mandatory SPDX header.Source: Coding guidelines
skills/nemoclaw-user-configure-inference/references/set-up-sub-agent.md (1)
1-4:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the required SPDX license header at the top of this Markdown file.
This file is missing the mandated SPDX copyright and license header comment block.
As per coding guidelines, “All source files must include an SPDX license header … (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 `@skills/nemoclaw-user-configure-inference/references/set-up-sub-agent.md` around lines 1 - 4, This Markdown file lacks the required SPDX license header; add the mandated SPDX copyright and license header as an HTML comment block at the very top of the file (above the "Set Up Task-Specific Sub-Agents" heading) so the header is present in the rendered source, e.g., an HTML comment containing the SPDX short identifier and copyright line; ensure the comment is the first thing in the file and follows the project's exact SPDX text format.Source: Coding guidelines
.agents/skills/nemoclaw-user-reference/references/commands.md (2)
1-4:⚠️ Potential issue | 🟠 Major | ⚡ Quick winSPDX header is required here.
This Markdown file needs the SPDX copyright/license header comment block.
As per coding guidelines, “All source files must include an SPDX license header … (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 @.agents/skills/nemoclaw-user-reference/references/commands.md around lines 1 - 4, This Markdown file is missing the required SPDX license header; add an SPDX comment block at the very top using HTML comment syntax (<!-- ... -->) with the appropriate SPDX-License-Identifier and copyright/ownership line so the file complies with the guideline; ensure the header appears before any content such as the "# NemoClaw CLI Commands Reference" title or the "import { AgentOnly }" line.Source: Coding guidelines
1-4:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAvoid direct edits to autogenerated
.agentsskill documentation.Changes for this content should be made in source docs and then regenerated.
As per coding guidelines, “Autogenerated user skills under
.agents/skills/nemoclaw-user-*/*.mdmust never be edited directly”.🤖 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 - 4, This file is autogenerated and must not be edited directly: revert changes to the header "# NemoClaw CLI Commands Reference" and the import line "import { AgentOnly }" in the autogenerated output, then make your content changes in the original source documentation (the source Markdown/template that generates this file) and run the documentation generator/regeneration step to produce updated contents for the autogenerated file.Source: Coding guidelines
.agents/skills/nemoclaw-user-reference/references/network-policies.md (2)
1-4:⚠️ Potential issue | 🟠 Major | ⚡ Quick winMissing SPDX license header.
Add the required Markdown SPDX header comment block at the top of the file.
As per coding guidelines, “All source files must include an SPDX license header … (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 @.agents/skills/nemoclaw-user-reference/references/network-policies.md around lines 1 - 4, Add the required SPDX license header as an HTML comment block at the very top of this Markdown file (above the "# Network Policies" heading); specifically insert an HTML comment containing the SPDX-License-Identifier (and optional copyright line if your project requires it) such as <!-- SPDX-License-Identifier: <LICENSE> --> so the file complies with the project's "All source files must include an SPDX license header" guideline.Source: Coding guidelines
1-4:⚠️ Potential issue | 🟠 Major | ⚡ Quick winThis autogenerated
.agentsdoc should not be edited manually.Please apply the change in the source docs and regenerate this artifact.
As per coding guidelines, “Autogenerated user skills under
.agents/skills/nemoclaw-user-*/*.mdmust never be edited directly”.🤖 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/network-policies.md around lines 1 - 4, The file "network-policies.md" under the .agents output is autogenerated and must not be edited directly; instead make the change in the original source docs that produce the "Network Policies" output (the upstream source for the Network Policies doc), then run the documentation generation/regeneration step to recreate the autogenerated .agents artifact so the change is reflected; do not modify the autogenerated ".agents" file itself.Source: Coding guidelines
.agents/skills/nemoclaw-user-reference/references/architecture.md (2)
1-4:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRegenerate this
.agentspage from source instead of editing it directly.This file is in the autogenerated user-skills namespace and should not be hand-edited.
As per coding guidelines, “Autogenerated user skills under
.agents/skills/nemoclaw-user-*/*.mdmust never be edited directly”.🤖 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/architecture.md around lines 1 - 4, This autogenerated page (architecture.md under the nemoClaw user skill namespace) was edited directly; revert those manual edits and regenerate the file from the canonical source (the user-skill generator/template or blueprint repository) instead of editing .agents/skills/nemoclaw-user-*/*.md by hand, then commit the upstream source change (e.g., the template or source YAML/markdown used by the generator) and re-run the generation/build script so the regenerated file reflects the intended changes.Source: Coding guidelines
1-4:⚠️ Potential issue | 🟠 Major | ⚡ Quick winMissing required SPDX header in Markdown file.
Please add the mandated SPDX copyright and license header comments at the top.
As per coding guidelines, “All source files must include an SPDX license header … (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 @.agents/skills/nemoclaw-user-reference/references/architecture.md around lines 1 - 4, Add the required SPDX license header as an HTML comment at the very top of the Markdown file (before the "# Architecture Details" heading) in .agents/skills/nemoclaw-user-reference/references/architecture.md; include both the SPDX copyright text and the SPDX-License-Identifier (e.g., a copyright owner line and the license identifier) in the comment so the file complies with the project's "All source files must include an SPDX license header" rule.Source: Coding guidelines
.agents/skills/nemoclaw-user-configure-inference/references/inference-options.md (2)
1-4:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the required SPDX header block.
The Markdown SPDX copyright/license header is missing from this file.
As per coding guidelines, “All source files must include an SPDX license header … (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 @.agents/skills/nemoclaw-user-configure-inference/references/inference-options.md around lines 1 - 4, Add an SPDX license header as an HTML comment at the very top of this Markdown file (before the "# NemoClaw Inference Options" heading and any imports) to satisfy the "All source files must include an SPDX license header" rule; include both SPDX-FileCopyrightText and SPDX-License-Identifier fields in the comment block so the file .agents/skills/nemoclaw-user-configure-inference/references/inference-options.md has the required SPDX metadata.Source: Coding guidelines
1-4:⚠️ Potential issue | 🟠 Major | ⚡ Quick winDo not edit autogenerated
.agentsskill docs directly.This path is designated as autogenerated user-skill output and should be regenerated from source docs instead of being manually modified.
As per coding guidelines, “Autogenerated user skills under
.agents/skills/nemoclaw-user-*/*.mdmust never be edited directly”.🤖 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 - 4, This file (the doc titled "NemoClaw Inference Options" containing the import line "import { AgentOnly } from \"../_components/AgentGuide\"") is an autogenerated user-skill doc and must not be edited directly; revert any manual changes to this inference-options.md, then update the original source documentation or the skill-docs generator that produces this file (edit the corresponding nemoclaw-user source doc or generator input) and re-run the docs generation process so the change is applied upstream rather than editing the autogenerated file.Source: Coding guidelines
skills/nemoclaw-user-reference/references/commands.md (1)
1-1:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the required SPDX header at the top of this Markdown file.
This file is missing the mandated Markdown SPDX header block. Please add the two HTML-comment SPDX lines before the title on Line 1.
As per coding guidelines, all
*.mdfiles must include SPDX headers using HTML comments (SPDX-FileCopyrightTextandSPDX-License-Identifier).🤖 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 `@skills/nemoclaw-user-reference/references/commands.md` at line 1, Add the required SPDX header block as two HTML comments immediately before the document title "# NemoClaw CLI Commands Reference": include an SPDX-FileCopyrightText line with the copyright holder/year and an SPDX-License-Identifier line with the license identifier (e.g., "SPDX-License-Identifier: Apache-2.0"), ensuring both are placed above the title line in this Markdown file.Source: Coding guidelines
skills/nemoclaw-user-reference/references/network-policies.md (1)
1-1:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the required SPDX header at the top of this Markdown file.
This Markdown page is missing the required SPDX license header block before the H1 on Line 1.
As per coding guidelines, all
*.mdfiles must include SPDX headers using HTML comments (SPDX-FileCopyrightTextandSPDX-License-Identifier).🤖 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 `@skills/nemoclaw-user-reference/references/network-policies.md` at line 1, This Markdown file is missing the SPDX header: add an HTML comment block with SPDX-FileCopyrightText and SPDX-License-Identifier immediately above the existing H1 "# Network Policies" so the header precedes the content; ensure the two SPDX lines use the exact keys "SPDX-FileCopyrightText" and "SPDX-License-Identifier" and include the correct copyright text and license identifier per project guidelines.Source: Coding guidelines
🟠 Major comments (23)
skills/nemoclaw-user-configure-security/references/best-practices.md-1-4 (1)
1-4:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the required SPDX header to this Markdown file.
The SPDX license header required for Markdown files is missing.
🤖 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 `@skills/nemoclaw-user-configure-security/references/best-practices.md` around lines 1 - 4, This Markdown file is missing the SPDX license header; add an HTML comment SPDX header as the very first line (e.g. <!-- SPDX-License-Identifier: MIT --> or the project's actual SPDX identifier) so it appears before the "# NemoClaw..." title and any code/import lines (refer to this file's top content and the existing import { AgentOnly } line to locate where to insert it).Source: Coding guidelines
skills/nemoclaw-user-configure-security/references/openclaw-controls.md-1-2 (1)
1-2:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the required SPDX header to this Markdown file.
This Markdown file is missing the required SPDX copyright and license header.
🤖 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 `@skills/nemoclaw-user-configure-security/references/openclaw-controls.md` around lines 1 - 2, This file titled "OpenClaw Security Controls Beyond NemoClaw's Scope" is missing the required SPDX header; add a standard SPDX copyright and license header as the first lines of the Markdown (above the existing title), including the copyright owner/year statement and an SPDX-License-Identifier (e.g., MIT, Apache-2.0, etc.) so the file has both copyright and license metadata at the top.Source: Coding guidelines
skills/nemoclaw-user-manage-policy/references/integration-policy-examples.md-1-4 (1)
1-4:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the required SPDX header to this Markdown file.
The file is missing the mandatory SPDX header comment block for Markdown sources.
🤖 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 `@skills/nemoclaw-user-manage-policy/references/integration-policy-examples.md` around lines 1 - 4, Add the required SPDX header comment block to the top of the Markdown file by inserting an HTML comment containing both the SPDX copyright/text and the SPDX-License-Identifier (for example <!-- SPDX-FileCopyrightText: YourOrg or Author --> and <!-- SPDX-License-Identifier: <LICENSE> -->) so the file (skills/nemoclaw-user-manage-policy/references/integration-policy-examples.md) includes the mandatory SPDX metadata in an HTML comment at the very beginning.Source: Coding guidelines
skills/nemoclaw-user-configure-security/references/credential-storage.md-1-4 (1)
1-4:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the required SPDX header to this Markdown file.
Please include the mandated Markdown SPDX header comment block in this file.
🤖 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 `@skills/nemoclaw-user-configure-security/references/credential-storage.md` around lines 1 - 4, Add the required Markdown SPDX header comment block as the very first lines of the file (above the "# Credential Storage" heading and the import line). Insert a single HTML comment SPDX tag in the form <!-- SPDX-License-Identifier: <LICENSE> --> (replace <LICENSE> with the correct identifier for this repository) so the file contains the mandated SPDX header before any other content such as the "# Credential Storage" heading or the import { AgentOnly } line.Source: Coding guidelines
skills/nemoclaw-user-manage-sandboxes/references/messaging-channels.md-1-3 (1)
1-3:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the mandatory SPDX license header.
Line 1 starts with the heading and Line 3 imports a component, but the required Markdown SPDX HTML comments are absent.
As per coding guidelines: “All source files must include an SPDX license header … (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 `@skills/nemoclaw-user-manage-sandboxes/references/messaging-channels.md` around lines 1 - 3, Add the required SPDX license header as an HTML comment at the top of the Markdown file: insert the SPDX header comment before the existing content (before the "# Messaging Channels" heading) so the file contains the SPDX notice in HTML comment form; ensure it appears above the import line "import { AgentOnly } from \"../_components/AgentGuide\";" and follows the project's standard SPDX text exactly.Source: Coding guidelines
skills/nemoclaw-user-manage-sandboxes/references/install-plugins-hermes.md-1-2 (1)
1-2:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd SPDX header to this new Markdown page.
The file begins at Line 1 without the required SPDX HTML comment header.
As per coding guidelines: “All source files must include an SPDX license header … (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 `@skills/nemoclaw-user-manage-sandboxes/references/install-plugins-hermes.md` around lines 1 - 2, Add the required SPDX HTML comment header at the top of the Markdown file (above the existing "# Install Hermes Plugins" heading); insert an HTML comment containing the SPDX license identifier (e.g., SPDX-License-Identifier: <LICENSE>) as per project guidelines so every source file includes the SPDX header.Source: Coding guidelines
skills/nemoclaw-user-manage-sandboxes/references/backup-restore.md-1-3 (1)
1-3:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd required SPDX header at the top of the file.
Line 1 starts with content/imports and does not include the mandatory SPDX HTML comments.
As per coding guidelines: “All source files must include an SPDX license header … (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 `@skills/nemoclaw-user-manage-sandboxes/references/backup-restore.md` around lines 1 - 3, The file is missing the required SPDX license header; add an HTML comment SPDX header as the very first lines of the Markdown (above the "# Backup and Restore Workspace Files" title and above the import statement), e.g. an HTML comment with the SPDX short identifier and copyright line per repo policy so the file contains the mandatory SPDX header before any content like the existing import { AgentOnly } or the document title.Source: Coding guidelines
skills/nemoclaw-user-manage-sandboxes/references/runtime-controls.md-1-3 (1)
1-3:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd SPDX header at the top of this file.
The required Markdown SPDX HTML comments are missing before the page content.
As per coding guidelines: “All source files must include an SPDX license header … (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 `@skills/nemoclaw-user-manage-sandboxes/references/runtime-controls.md` around lines 1 - 3, Add the required SPDX license header as HTML comments at the very top of the Markdown file (before the "# Runtime Controls and Sandbox Mutability" heading and before the import line). Insert two HTML comment lines: one for copyright/ownership (e.g. <!-- SPDX-FileCopyrightText: YEAR YourNameOrOrg -->) and one for the license identifier (e.g. <!-- SPDX-License-Identifier: MIT -->), ensuring they appear exactly as HTML comments so Markdown renders correctly; place them above the existing content/import statements in runtime-controls.md.Source: Coding guidelines
skills/nemoclaw-user-manage-sandboxes/SKILL.md-1-6 (1)
1-6:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd required SPDX header to this Markdown file.
Line 1 starts directly with frontmatter; the required Markdown SPDX HTML comments are missing.
Suggested fix
+<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. --> +<!-- SPDX-License-Identifier: Apache-2.0 --> --- name: "nemoclaw-user-manage-sandboxes"As per coding guidelines: “All source files must include an SPDX license header … (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 `@skills/nemoclaw-user-manage-sandboxes/SKILL.md` around lines 1 - 6, Insert an SPDX license HTML comment at the top of SKILL.md before the existing YAML frontmatter; add an SPDX-License-Identifier line with the project license (SPDX-License-Identifier: Apache-2.0) and include the required SPDX copyright tag per repo convention, ensuring the comment is an HTML comment (<!-- ... -->) so it remains valid in Markdown and sits above the frontmatter block.Source: Coding guidelines
skills/nemoclaw-user-manage-sandboxes/references/workspace-files.md-1-4 (1)
1-4:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the required SPDX license header at the top of this Markdown file.
This file is missing the required Markdown SPDX header 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 `@skills/nemoclaw-user-manage-sandboxes/references/workspace-files.md` around lines 1 - 4, Add the missing SPDX license header as the very first line of this Markdown file (before the existing import { AgentOnly } line); insert a Markdown/HTML comment-style SPDX identifier using the appropriate license id for the project (e.g., MIT or Apache-2.0) so the file starts with the SPDX comment header.Source: Coding guidelines
skills/nemoclaw-user-overview/references/how-it-works.md-1-5 (1)
1-5:⚠️ Potential issue | 🟠 Major | ⚡ Quick winSPDX header is missing from this Markdown source file.
Please add the required Markdown SPDX HTML header lines.
🤖 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 `@skills/nemoclaw-user-overview/references/how-it-works.md` around lines 1 - 5, The file "NemoClaw Architecture Overview" (starts with the heading "NemoClaw Architecture Overview" and an import line 'import { AgentCli, AgentOnly } from "../_components/AgentGuide";') is missing the required SPDX HTML header; add the SPDX header lines at the very top of the Markdown file (HTML comment lines with license identifier and copyright notice per project policy) so the file begins with the SPDX header before the existing heading.Source: Coding guidelines
skills/nemoclaw-user-overview/references/overview.md-1-5 (1)
1-5:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRequired SPDX Markdown header is missing.
Please include the SPDX copyright and license 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 `@skills/nemoclaw-user-overview/references/overview.md` around lines 1 - 5, The file is missing the required SPDX HTML comment header; add the SPDX copyright and license comments at the very top of the file (before the "# Overview of NVIDIA NemoClaw" header and any imports) using the standard format (e.g. <!-- SPDX-FileCopyrightText: <year> <copyright holder> --> and <!-- SPDX-License-Identifier: <license-id> -->), ensuring the comments precede the existing content so tools can detect the license.Source: Coding guidelines
skills/nemoclaw-user-overview/references/ecosystem-hermes.md-1-4 (1)
1-4:⚠️ Potential issue | 🟠 Major | ⚡ Quick winMissing required SPDX header in this Markdown file.
Please add the mandated Markdown SPDX HTML comments at the top of the file.
🤖 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 `@skills/nemoclaw-user-overview/references/ecosystem-hermes.md` around lines 1 - 4, Add the required SPDX Markdown HTML comments at the top of ecosystem-hermes.md by inserting the SPDX header lines (e.g. an <!-- SPDX-FileCopyrightText: ... --> comment and an <!-- SPDX-License-Identifier: ... --> comment) immediately before the existing "# Ecosystem" content so the file contains both the copyright attribution and the license identifier as mandated.Source: Coding guidelines
skills/nemoclaw-user-overview/references/ecosystem.md-1-5 (1)
1-5:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd SPDX header comments required for Markdown files.
This file does not include the required SPDX copyright and license header.
🤖 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 `@skills/nemoclaw-user-overview/references/ecosystem.md` around lines 1 - 5, Add the required SPDX header comments at the top of the Markdown (above the "# Ecosystem" heading) by inserting SPDX-FileCopyrightText and SPDX-License-Identifier HTML comment lines; replace YEAR, COPYRIGHT_HOLDER and LICENSE_IDENTIFIER with the correct values for this project (e.g., <!-- SPDX-FileCopyrightText: 2026 Acme Corp --> and <!-- SPDX-License-Identifier: Apache-2.0 -->) so the file containing the "Ecosystem" section includes the proper copyright and license metadata.Source: Coding guidelines
skills/nemoclaw-user-overview/references/release-notes.md-1-6 (1)
1-6:⚠️ Potential issue | 🟠 Major | ⚡ Quick winSPDX header is required but missing in this Markdown file.
Please add the required SPDX HTML comment header 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 `@skills/nemoclaw-user-overview/references/release-notes.md` around lines 1 - 6, Add the required SPDX HTML comment header as the very first line of this Markdown file (above the "# Release Notes" heading) — insert an SPDX comment like <!-- SPDX-License-Identifier: Apache-2.0 --> (or the repository’s actual SPDX identifier) at the top of release-notes.md so the file contains the required machine-readable license header.Source: Coding guidelines
skills/nemoclaw-user-overview/SKILL.md-1-5 (1)
1-5:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the required SPDX header for Markdown files.
This Markdown file is missing the required SPDX header comments.
Suggested fix
+<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. --> +<!-- SPDX-License-Identifier: Apache-2.0 --> --- name: "nemoclaw-user-overview" description: "Explains what NemoClaw covers: onboarding, lifecycle management, and agent operations within OpenShell containers, plus capabilities and why it exists. Use when users ask what NemoClaw is or what the project provides. For ecosystem placement or OpenShell-only paths, use the Ecosystem page; for internal mechanics, use How It Works. Trigger keywords - nemoclaw overview, openclaw always-on assistants, hermes agent, nvidia openshell, nvidia nemotron, nemoclaw ecosystem, nemohermes, nemoclaw vs openshell, run hermes openshell sandbox, openclaw openshell, sandboxed openclaw, how nemoclaw works, nemoclaw sandbox lifecycle blueprint, nemoclaw release notes, nemoclaw changelog." license: "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 `@skills/nemoclaw-user-overview/SKILL.md` around lines 1 - 5, Add the required SPDX header to the top of the Markdown file SKILL.md as an HTML comment that matches the declared license (Apache-2.0); insert a single line like <!-- SPDX-License-Identifier: Apache-2.0 --> before the YAML/frontmatter so the file contains the SPDX identifier consistent with the "license" field in the frontmatter and any repository licensing rules.Source: Coding guidelines
skills/nemoclaw-user-get-started/references/windows-preparation.md-1-1 (1)
1-1:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the required SPDX header for Markdown files.
Line 1 starts directly with content; this
.mdfile needs the required SPDX HTML comment header.🤖 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 `@skills/nemoclaw-user-get-started/references/windows-preparation.md` at line 1, Add the required SPDX HTML comment header to the top of the Markdown file that begins with the heading "# Prepare Windows for NemoClaw" so the file has an SPDX identifier (e.g. <!-- SPDX-License-Identifier: MIT -->) as the very first line before any content or headings.Source: Coding guidelines
skills/nemoclaw-user-get-started/references/prerequisites.md-1-3 (1)
1-3:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the required SPDX header for Markdown files.
Line 1 starts content without the mandatory SPDX HTML comment header for Markdown files.
🤖 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 `@skills/nemoclaw-user-get-started/references/prerequisites.md` around lines 1 - 3, Add the required SPDX HTML comment header at the very top of the Markdown file (prerequisites.md) so Line 1 is an SPDX comment like <!-- SPDX-License-Identifier: <LICENSE> --> (replace <LICENSE> with the project's actual identifier), ensuring the header appears before the "# Prerequisites" heading and uses the exact HTML comment format required for Markdown SPDX headers.Source: Coding guidelines
skills/nemoclaw-user-configure-inference/SKILL.md-1-1 (1)
1-1:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the required SPDX header comments to this Markdown file.
The mandatory SPDX header is missing.
🤖 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 `@skills/nemoclaw-user-configure-inference/SKILL.md` at line 1, Add the required SPDX header comments to the top of SKILL.md: insert HTML-style comment lines as the very first lines containing an SPDX-License-Identifier and an SPDX-FileCopyrightText entry with the correct license identifier and copyright holder/year for this project so the file has the mandated SPDX metadata.Source: Coding guidelines
skills/nemoclaw-user-configure-inference/references/inference-options.md-1-1 (1)
1-1:⚠️ Potential issue | 🟠 Major | ⚡ Quick winInsert the required SPDX header at the top of the file.
This Markdown file is missing the mandated SPDX copyright/license 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 `@skills/nemoclaw-user-configure-inference/references/inference-options.md` at line 1, Add the required SPDX header as HTML comment lines at the very top of the file (above the "# NemoClaw Inference Options" heading): include an SPDX-FileCopyrightText line with the correct copyright holder/year and an SPDX-License-Identifier line with the project's license identifier, ensuring both are in the form of HTML comments so they remain valid in Markdown.Source: Coding guidelines
skills/nemoclaw-user-deploy-remote/references/sandbox-hardening.md-1-1 (1)
1-1:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRe-add the mandatory SPDX header comments.
The SPDX copyright/license header is missing from this Markdown file.
As per coding guidelines: “All source files must include an SPDX license header … (use HTML comments for Markdown).”Suggested patch
+<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. --> +<!-- SPDX-License-Identifier: Apache-2.0 --> + # Sandbox Image Hardening🤖 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 `@skills/nemoclaw-user-deploy-remote/references/sandbox-hardening.md` at line 1, Add the missing SPDX header as HTML comments at the very top of this Markdown file (above the "Sandbox Image Hardening" heading): include an SPDX copyright line (SPDX-FileCopyrightText) and an SPDX-License-Identifier line using the required comment format for Markdown (HTML comments). Ensure the comments appear before any content so tools can detect the license, and use the repository's standard copyright holder and license identifier.Source: Coding guidelines
skills/nemoclaw-user-configure-inference/references/switch-inference-providers.md-1-4 (1)
1-4:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the required SPDX license header.
The required Markdown SPDX header block is missing from this file.
As per coding guidelines, “All source files must include an SPDX license header … (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 `@skills/nemoclaw-user-configure-inference/references/switch-inference-providers.md` around lines 1 - 4, The file is missing the required SPDX license header; add the repository's standard SPDX header as an HTML comment at the very top of skills/nemoclaw-user-configure-inference/references/switch-inference-providers.md (e.g. <!-- SPDX-License-Identifier: <LICENSE> -->), using the exact license identifier your repo requires and place it before the existing content (before "# Switch Inference Models at Runtime") so the Markdown file complies with the "use HTML comments for Markdown" guideline.Source: Coding guidelines
skills/nemoclaw-user-configure-inference/references/tool-calling-reliability.md-1-4 (1)
1-4:⚠️ Potential issue | 🟠 Major | ⚡ Quick winInsert the SPDX header comment block.
This Markdown file currently lacks the required SPDX copyright/license header.
As per coding guidelines, “All source files must include an SPDX license header … (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 `@skills/nemoclaw-user-configure-inference/references/tool-calling-reliability.md` around lines 1 - 4, This Markdown file (the document starting with the heading "Tool-Calling Reliability for Local Inference") lacks the required SPDX license header; add the standard SPDX header as an HTML comment at the very top of the file (before the "# Tool-Calling Reliability for Local Inference" heading) following the project's license template so every source file includes the SPDX copyright/license block.Source: Coding guidelines
🟡 Minor comments (2)
skills/nemoclaw-user-manage-sandboxes/references/runtime-controls.md-80-80 (1)
80-80:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winCorrect duplicated command token in Hermes CLI sentence.
Line 80 currently reads “every
nemoclawandnemoclawcommand,” which is ambiguous and likely an accidental duplication.🤖 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 `@skills/nemoclaw-user-manage-sandboxes/references/runtime-controls.md` at line 80, The sentence in runtime-controls.md currently contains a duplicated command token "every `nemoclaw` and `nemoclaw` command"; update that phrase to the correct pair by replacing the second backticked token with the Hermes CLI token (change "every `nemoclaw` and `nemoclaw` command" to "every `nemoclaw` and `hermes` command") so the CLI reference line correctly mentions both tools.skills/nemoclaw-user-manage-sandboxes/SKILL.md-22-23 (1)
22-23:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winFix duplicated command name in Hermes CLI boundary sentence.
Line 22 repeats
nemoclawtwice, which makes the command boundary unclear for readers.🤖 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 `@skills/nemoclaw-user-manage-sandboxes/SKILL.md` around lines 22 - 23, The sentence in SKILL.md repeats the command name `nemoclaw` and should instead list the three distinct CLI boundaries; update the text in the CLI Selection Guide sentence so it reads that the boundary is between `nemoclaw`, `nemoclaw-user-reference`, and `openshell` (replace the duplicated `nemoclaw` with `nemoclaw-user-reference` to match the referenced skill).
🧹 Nitpick comments (3)
skills/nemoclaw-user-overview/SKILL.md (1)
3-3: ⚡ Quick winUse
NVIDIAin all caps in trigger keywords.
nvidia openshellandnvidia nemotronshould beNVIDIA ...to match the word-list rule.🤖 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 `@skills/nemoclaw-user-overview/SKILL.md` at line 3, Update the trigger keywords in the description field so all occurrences of "nvidia" are uppercase "NVIDIA"; specifically edit the description's trigger keywords list (the string under the description key in SKILL.md) and replace "nvidia openshell" and "nvidia nemotron" with "NVIDIA openshell" and "NVIDIA nemotron" (and any other lowercase "nvidia" tokens) to comply with the word-list rule.Source: Coding guidelines
skills/nemoclaw-user-overview/references/ecosystem-hermes.md (1)
15-16: ⚡ Quick winRemove emoji from technical documentation content.
The mermaid node labels include emoji. The docs guideline forbids emoji in technical prose/content.
🤖 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 `@skills/nemoclaw-user-overview/references/ecosystem-hermes.md` around lines 15 - 16, Remove the emoji characters from the mermaid node labels so technical prose contains no emoji: update the NC and OS node definitions (e.g. NC["🦞 NVIDIA NemoClaw<br/>CLI, blueprint"] and OS["🐚 NVIDIA OpenShell<br/>Gateway, policy, inference routing"]) to plain text such as NC["NVIDIA NemoClaw<br/>CLI, blueprint"] and OS["NVIDIA OpenShell<br/>Gateway, policy, inference routing"]; also scan nearby mermaid nodes in the same file for any other emoji and remove them for consistency.Source: Coding guidelines
docs/about/release-notes.mdx (1)
20-24: ⚡ Quick winSplit multi-sentence bullets into one sentence per source line.
Line 20 through Line 24 each contain multiple sentences on one line; docs style requires one sentence per line for readable diffs.
🤖 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, Each bullet currently contains multiple sentences; split each bullet so every sentence is on its own source line (i.e., one sentence per list item line) while preserving the leading "-" and links and keeping sentences in the same order; update the four bullets that start with "OpenClaw runtime guidance...", "Onboarding and sandbox lifecycle...", "Local inference setup...", and "Messaging and day-two CLI operations..." so each sentence becomes a separate line (maintain links like [Architecture], [NemoClaw CLI Commands Reference], [NemoClaw Inference Options], and [Messaging Channels] in their original sentences).Source: Coding guidelines
Contributor
There was a problem hiding this comment.
Actionable comments posted: 7
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (10)
.agents/skills/nemoclaw-contributor-update-docs/SKILL.md (1)
1-5:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the required SPDX license header for this Markdown source file.
This file is missing the mandatory SPDX header in Markdown-comment form immediately after frontmatter.
As per coding guidelines, "
**/*.{...md...}files 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-contributor-update-docs/SKILL.md around lines 1 - 5, The SKILL.md file is missing the required SPDX license header; add an HTML-comment SPDX header immediately after the YAML frontmatter (i.e., directly after the closing ---) in the SKILL.md document so Markdown processors see the frontmatter first and the SPDX header second; ensure the comment contains the SPDX-License-Identifier and any required copyright/owner token per project policy.Source: Coding guidelines
.agents/skills/nemoclaw-user-reference/references/troubleshooting.md (1)
1-3:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd missing SPDX metadata header.
This Markdown source is missing the mandatory SPDX copyright and license lines.
As per coding guidelines: all
**/*.{... ,md,mdx,...}files must include SPDX headers, and Markdown files must use HTML comments.Suggested patch
+<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. --> +<!-- SPDX-License-Identifier: Apache-2.0 --> + # Troubleshooting🤖 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/troubleshooting.md around lines 1 - 3, Add the missing SPDX metadata header to the top of this Markdown document by inserting the required SPDX copyright and license lines as HTML comments (e.g., <!-- SPDX-FileCopyrightText: ... --> and <!-- SPDX-License-Identifier: ... -->) above the "Troubleshooting" title so the file contains the mandated SPDX header format for Markdown files.Source: Coding guidelines
.agents/skills/nemoclaw-user-configure-inference/references/switch-inference-providers.md (1)
1-4:⚠️ Potential issue | 🟠 Major | ⚡ Quick winInsert SPDX header comments before the title.
The required SPDX copyright and license header is missing.
As per coding guidelines: all
**/*.{... ,md,mdx,...}files must include SPDX headers, using HTML comments for Markdown.Suggested patch
+<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. --> +<!-- SPDX-License-Identifier: Apache-2.0 --> + # Switch Inference Models at Runtime🤖 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/switch-inference-providers.md around lines 1 - 4, Add the required SPDX header as HTML comments at the very top of the Markdown file (before the title line "# Switch Inference Models at Runtime"); include both an SPDX-FileCopyrightText comment with the correct year/owner and an SPDX-FileCopyrightText comment or SPDX-License-Identifier line for the license (e.g., SPDX-License-Identifier), then save — locate the file area that contains the title and the subsequent import line "import { AgentOnly } from \"../_components/AgentGuide\";" to ensure the SPDX comments are placed immediately above the title.Source: Coding guidelines
.agents/skills/nemoclaw-user-configure-inference/references/inference-options.md (1)
1-4:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd the required SPDX header at the top of this Markdown file.
This file is missing the required SPDX copyright and license header for Markdown sources.
As per coding guidelines: all
**/*.{... ,md,mdx,...}files must include SPDX headers, and for Markdown the header must use HTML comments.Suggested patch
+<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. --> +<!-- SPDX-License-Identifier: Apache-2.0 --> + # NemoClaw Inference Options🤖 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 - 4, Add the required SPDX header as an HTML comment at the very top of this Markdown file (before the "# NemoClaw Inference Options" title); the header must include the SPDX copyright statement and an SPDX-License-Identifier (e.g. <!-- SPDX-FileCopyrightText: <year> <owner> --> and <!-- SPDX-License-Identifier: <license-id> -->) following the project guidance so the file contains the proper SPDX metadata.Source: Coding guidelines
.agents/skills/nemoclaw-user-manage-policy/references/integration-policy-examples.md (2)
1-1:⚠️ Potential issue | 🟠 Major | ⚡ Quick winSPDX license header is required for this Markdown file.
The required SPDX copyright/license header is missing at the top of this source file.
As per coding guidelines, "All source files must include an SPDX license header ... (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 @.agents/skills/nemoclaw-user-manage-policy/references/integration-policy-examples.md at line 1, This Markdown file ("# Common NemoClaw Integration Policy Examples" heading) is missing the required SPDX license header; add an HTML comment SPDX header at the very top of the file (e.g. <!-- SPDX-FileCopyrightText: ... and/or <!-- SPDX-License-Identifier: ... -->) following your project's standard format, ensuring the SPDX copyright and license identifier are present before the "# Common NemoClaw Integration Policy Examples" heading.Source: Coding guidelines
1-374:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAutogenerated skill content should be regenerated, not hand-edited.
This path is an autogenerated user-skill file; please revert direct edits and regenerate from the canonical docs conversion flow.
As per coding guidelines, "Autogenerated user skills under
.agents/skills/nemoclaw-user-*/*.mdmust never be edited directly".🤖 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-manage-policy/references/integration-policy-examples.md around lines 1 - 374, This file is an autogenerated user-skill Markdown that was edited directly; revert your manual changes to restore the original generated content and regenerate the skill via the canonical docs conversion flow instead of hand-editing; specifically remove any edits around the autogenerated notice and the AgentOnly components (AgentOnly variant="openclaw" / variant="hermes") and re-run the generator that produces integration-policy-examples.md so the file matches the canonical source and future auto-updates.Source: Coding guidelines
.agents/skills/nemoclaw-user-reference/references/network-policies.md (2)
1-1:⚠️ Potential issue | 🟠 Major | ⚡ Quick winMissing SPDX header in Markdown source.
Line 1 should include the required SPDX copyright and license header in Markdown-comment form.
As per coding guidelines, "All source files must include an SPDX license header ... (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 @.agents/skills/nemoclaw-user-reference/references/network-policies.md at line 1, Add the required SPDX license header as an HTML comment at the very top of the Markdown source (above the existing "# Network Policies" heading); insert a single-line HTML comment containing the copyright owner and SPDX identifier (for example: <!-- Copyright 2026 ACME Corp. SPDX-License-Identifier: Apache-2.0 -->) so the file begins with the proper SPDX header in Markdown-comment form.Source: Coding guidelines
1-130:⚠️ Potential issue | 🟠 Major | ⚡ Quick winDo not edit autogenerated user-skill files directly.
This file is under
.agents/skills/nemoclaw-user-*/*.md, so direct edits should be reverted and regenerated from the docs/source pipeline instead.As per coding guidelines, "Autogenerated user skills under
.agents/skills/nemoclaw-user-*/*.mdmust never be edited directly".🤖 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/network-policies.md around lines 1 - 130, This edited "Network Policies" user-skill (network-policies.md) is autogenerated and must not be edited directly; revert the changes to this file, update the source-of-truth in the docs/source pipeline that generates the `.agents/skills/nemoclaw-user-*/*.md` artifacts, and regenerate the skill artifacts (run the docs build/generation job) so the corrected content flows into network-policies.md; reference the "Network Policies" header to locate the autogenerated file and include a brief commit message noting "Revert direct edit — regenerate from docs/source".Source: Coding guidelines
.agents/skills/nemoclaw-user-reference/references/commands.md (2)
1-1:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRequired SPDX header is missing.
Add the SPDX copyright and license header at the top of this Markdown source file.
As per coding guidelines, "All source files must include an SPDX license header ... (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 @.agents/skills/nemoclaw-user-reference/references/commands.md at line 1, Add an SPDX license header as an HTML comment at the very top of the Markdown file (above the "# NemoClaw CLI Commands Reference" title) using the SPDX fields required by our guidelines (e.g., a copyright line with year and owner and an SPDX-License-Identifier), so the file contains a leading <!-- ... --> comment that includes the SPDX copyright and license identifier.Source: Coding guidelines
1-2010:⚠️ Potential issue | 🟠 Major | ⚡ Quick winDirect edits to autogenerated skill docs are not allowed.
This file should be updated via the docs-to-skills generation path, not by manual edits in
.agents/skills/nemoclaw-user-*.As per coding guidelines, "Autogenerated user skills under
.agents/skills/nemoclaw-user-*/*.mdmust never be edited directly".🤖 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 - 2010, This file was edited directly but is autogenerated; revert the manual changes to "NemoClaw CLI Commands Reference" under the .agents/skills/nemoclaw-user-* output, then make your content change in the canonical docs source used by the docs-to-skills generator (not in the generated markdown), run the docs-to-skills generation pipeline to regenerate the outputs (so files like the generated commands.md are updated), commit the regenerated files only, and ensure CI/regen checks pass so future edits come via the generator rather than direct edits to the autogenerated skill docs.Source: Coding guidelines
🧹 Nitpick comments (1)
.agents/skills/nemoclaw-contributor-update-docs/SKILL.md (1)
184-186: ⚡ Quick winRewrite this updated note to active voice and keep one full sentence on one source line.
The new text uses passive voice (“is refreshed...”) and splits a single sentence across multiple lines.
As per coding guidelines, "Active voice required" and "One sentence per line in source."
🤖 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-contributor-update-docs/SKILL.md around lines 184 - 186, Rewrite the note that begins "Do not include the root `skills/` directory as an output target..." into active voice and place the entire sentence on a single source line; for example, change passive phrasing ("That directory is refreshed by a separate process and must not be updated by this skill.") to active voice ("A separate process refreshes the skills/ directory, so this skill must not update it.") and ensure the result is one full sentence on one line in SKILL.md.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
@.agents/skills/nemoclaw-user-configure-security/references/best-practices.md:
- Line 428: The Markdown table cell text beginning with "Default | Startup
auto-pairing and `connect`-time approval share one policy." contains three
sentences on one line; split it so each sentence lives on its own line in the
same table cell (e.g., one line for "Default | Startup auto-pairing and
`connect`-time approval share one policy.", one line for "NemoClaw approves
devices with `clientId` set to `openclaw-control-ui` or `clientMode` set to
`webchat` or `cli`.", and one line for "It only approves for `operator.pairing`,
`operator.read`, and `operator.write` scopes; all other clients or scopes are
rejected and logged.").
- Line 465: The paragraph describing path classifiers and credential patterns
must be split so each sentence is on its own line; update the Markdown around
the isMemoryPath() description so the sentence about three path classifiers and
credential-shaped text is one line and the following sentence enumerating the
three classifiers (referencing MEMORY_PATH_SEGMENTS, MEMORY_BASENAMES, and
MEMORY_RELATIVE_PREFIXES) is on its own line; ensure the three classifier
categories remain intact and keep the symbol names (isMemoryPath(),
MEMORY_PATH_SEGMENTS, MEMORY_BASENAMES, MEMORY_RELATIVE_PREFIXES) unchanged for
clarity.
In @.agents/skills/nemoclaw-user-manage-sandboxes/SKILL.md:
- Line 116: The sentence in the autogenerated SKILL.md uses passive voice;
update the source docs file docs/manage-sandboxes/lifecycle.mdx to use active
voice (e.g., change "Gateway and dashboard cleanup is scoped by sandbox name and
port." to "NemoClaw scopes gateway and dashboard cleanup by sandbox name and
port.") and regenerate artifacts so the change propagates into
.agents/skills/nemoclaw-user-manage-sandboxes/SKILL.md; edit the lifecycle.mdx
entry where that sentence appears and run docs-to-skills.py to produce the
updated SKILL.md.
In @.agents/skills/nemoclaw-user-overview/references/how-it-works.md:
- Line 68: Change the passive sentence "Runtime context is prepended as system
guidance, so sandbox and policy instructions stay active without appearing in
the visible chat transcript." in the source docs file to active voice (e.g.,
"The plugin prepends runtime context as system guidance, so sandbox and policy
instructions stay active without appearing in the visible chat transcript.");
make the edit in docs/about/how-it-works.mdx (not the autogenerated .agents/...
file) and keep the rest of the sentence meaning intact.
In `@docs/reference/commands.mdx`:
- Line 1819: Update the passive phrase in the table row for
NEMOCLAW_MINIMAL_BOOTSTRAP so it uses active voice: replace "Existing files are
not deleted" with an active construction such as "This setting does not delete
existing files" (or "It does not delete existing files") in the description cell
for NEMOCLAW_MINIMAL_BOOTSTRAP to convey the same meaning in active voice.
In `@docs/security/best-practices.mdx`:
- Line 453: The table cell containing "Default | Startup auto-pairing and
`connect`-time approval share one policy. NemoClaw approves devices with
`clientId` set to `openclaw-control-ui` or `clientMode` set to `webchat` or
`cli`, and only for `operator.pairing`, `operator.read`, and `operator.write`
scopes. All other clients or scopes are rejected and logged." should be split so
each sentence is on its own source line; edit the table row (the cell after the
first pipe) so the three sentences appear on three separate lines (keeping the
leading "Default |" and any required pipe separators intact) — ensure you
preserve escaping/backticks and punctuation exactly while breaking the
single-line cell into three lines.
- Line 490: The paragraph on memory path classifiers is two sentences and needs
to be split so each sentence is on its own Markdown line; edit the line
containing the descriptions of isMemoryPath(), MEMORY_PATH_SEGMENTS,
MEMORY_BASENAMES, and MEMORY_RELATIVE_PREFIXES so that each sentence becomes a
separate line (i.e., break after the first sentence describing what it covers
and then break the long sentence that lists the three classifiers into its own
line), preserving the exact identifiers and examples (`isMemoryPath()`,
`MEMORY_PATH_SEGMENTS`, `MEMORY_BASENAMES`, `MEMORY_RELATIVE_PREFIXES`, and the
example paths/basenames).
---
Outside diff comments:
In @.agents/skills/nemoclaw-contributor-update-docs/SKILL.md:
- Around line 1-5: The SKILL.md file is missing the required SPDX license
header; add an HTML-comment SPDX header immediately after the YAML frontmatter
(i.e., directly after the closing ---) in the SKILL.md document so Markdown
processors see the frontmatter first and the SPDX header second; ensure the
comment contains the SPDX-License-Identifier and any required copyright/owner
token per project policy.
In
@.agents/skills/nemoclaw-user-configure-inference/references/inference-options.md:
- Around line 1-4: Add the required SPDX header as an HTML comment at the very
top of this Markdown file (before the "# NemoClaw Inference Options" title); the
header must include the SPDX copyright statement and an SPDX-License-Identifier
(e.g. <!-- SPDX-FileCopyrightText: <year> <owner> --> and <!--
SPDX-License-Identifier: <license-id> -->) following the project guidance so the
file contains the proper SPDX metadata.
In
@.agents/skills/nemoclaw-user-configure-inference/references/switch-inference-providers.md:
- Around line 1-4: Add the required SPDX header as HTML comments at the very top
of the Markdown file (before the title line "# Switch Inference Models at
Runtime"); include both an SPDX-FileCopyrightText comment with the correct
year/owner and an SPDX-FileCopyrightText comment or SPDX-License-Identifier line
for the license (e.g., SPDX-License-Identifier), then save — locate the file
area that contains the title and the subsequent import line "import { AgentOnly
} from \"../_components/AgentGuide\";" to ensure the SPDX comments are placed
immediately above the title.
In
@.agents/skills/nemoclaw-user-manage-policy/references/integration-policy-examples.md:
- Line 1: This Markdown file ("# Common NemoClaw Integration Policy Examples"
heading) is missing the required SPDX license header; add an HTML comment SPDX
header at the very top of the file (e.g. <!-- SPDX-FileCopyrightText: ... and/or
<!-- SPDX-License-Identifier: ... -->) following your project's standard format,
ensuring the SPDX copyright and license identifier are present before the "#
Common NemoClaw Integration Policy Examples" heading.
- Around line 1-374: This file is an autogenerated user-skill Markdown that was
edited directly; revert your manual changes to restore the original generated
content and regenerate the skill via the canonical docs conversion flow instead
of hand-editing; specifically remove any edits around the autogenerated notice
and the AgentOnly components (AgentOnly variant="openclaw" / variant="hermes")
and re-run the generator that produces integration-policy-examples.md so the
file matches the canonical source and future auto-updates.
In @.agents/skills/nemoclaw-user-reference/references/commands.md:
- Line 1: Add an SPDX license header as an HTML comment at the very top of the
Markdown file (above the "# NemoClaw CLI Commands Reference" title) using the
SPDX fields required by our guidelines (e.g., a copyright line with year and
owner and an SPDX-License-Identifier), so the file contains a leading <!-- ...
--> comment that includes the SPDX copyright and license identifier.
- Around line 1-2010: This file was edited directly but is autogenerated; revert
the manual changes to "NemoClaw CLI Commands Reference" under the
.agents/skills/nemoclaw-user-* output, then make your content change in the
canonical docs source used by the docs-to-skills generator (not in the generated
markdown), run the docs-to-skills generation pipeline to regenerate the outputs
(so files like the generated commands.md are updated), commit the regenerated
files only, and ensure CI/regen checks pass so future edits come via the
generator rather than direct edits to the autogenerated skill docs.
In @.agents/skills/nemoclaw-user-reference/references/network-policies.md:
- Line 1: Add the required SPDX license header as an HTML comment at the very
top of the Markdown source (above the existing "# Network Policies" heading);
insert a single-line HTML comment containing the copyright owner and SPDX
identifier (for example: <!-- Copyright 2026 ACME Corp. SPDX-License-Identifier:
Apache-2.0 -->) so the file begins with the proper SPDX header in
Markdown-comment form.
- Around line 1-130: This edited "Network Policies" user-skill
(network-policies.md) is autogenerated and must not be edited directly; revert
the changes to this file, update the source-of-truth in the docs/source pipeline
that generates the `.agents/skills/nemoclaw-user-*/*.md` artifacts, and
regenerate the skill artifacts (run the docs build/generation job) so the
corrected content flows into network-policies.md; reference the "Network
Policies" header to locate the autogenerated file and include a brief commit
message noting "Revert direct edit — regenerate from docs/source".
In @.agents/skills/nemoclaw-user-reference/references/troubleshooting.md:
- Around line 1-3: Add the missing SPDX metadata header to the top of this
Markdown document by inserting the required SPDX copyright and license lines as
HTML comments (e.g., <!-- SPDX-FileCopyrightText: ... --> and <!--
SPDX-License-Identifier: ... -->) above the "Troubleshooting" title so the file
contains the mandated SPDX header format for Markdown files.
---
Nitpick comments:
In @.agents/skills/nemoclaw-contributor-update-docs/SKILL.md:
- Around line 184-186: Rewrite the note that begins "Do not include the root
`skills/` directory as an output target..." into active voice and place the
entire sentence on a single source line; for example, change passive phrasing
("That directory is refreshed by a separate process and must not be updated by
this skill.") to active voice ("A separate process refreshes the skills/
directory, so this skill must not update it.") and ensure the result is one full
sentence on one line in SKILL.md.
🪄 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: acad4e69-cfdd-4fcd-8cac-f3077f924a0b
📒 Files selected for processing (33)
.agents/skills/nemoclaw-contributor-update-docs/SKILL.md.agents/skills/nemoclaw-user-configure-inference/SKILL.md.agents/skills/nemoclaw-user-configure-inference/references/inference-options.md.agents/skills/nemoclaw-user-configure-inference/references/switch-inference-providers.md.agents/skills/nemoclaw-user-configure-inference/references/tool-calling-reliability.md.agents/skills/nemoclaw-user-configure-security/references/best-practices.md.agents/skills/nemoclaw-user-configure-security/references/credential-storage.md.agents/skills/nemoclaw-user-get-started/SKILL.md.agents/skills/nemoclaw-user-get-started/references/quickstart-hermes.md.agents/skills/nemoclaw-user-manage-policy/references/integration-policy-examples.md.agents/skills/nemoclaw-user-manage-sandboxes/SKILL.md.agents/skills/nemoclaw-user-overview/references/how-it-works.md.agents/skills/nemoclaw-user-reference/references/architecture.md.agents/skills/nemoclaw-user-reference/references/commands.md.agents/skills/nemoclaw-user-reference/references/network-policies.md.agents/skills/nemoclaw-user-reference/references/troubleshooting.mddocs/about/how-it-works.mdxdocs/get-started/quickstart-hermes.mdxdocs/get-started/quickstart.mdxdocs/inference/inference-options.mdxdocs/inference/switch-inference-providers.mdxdocs/inference/tool-calling-reliability.mdxdocs/inference/use-local-inference.mdxdocs/manage-sandboxes/lifecycle.mdxdocs/network-policy/integration-policy-examples.mdxdocs/reference/architecture.mdxdocs/reference/commands-nemohermes.mdxdocs/reference/commands.mdxdocs/reference/network-policies.mdxdocs/reference/troubleshooting.mdxdocs/security/best-practices.mdxdocs/security/credential-storage.mdxfern/fern.config.json
✅ Files skipped from review due to trivial changes (10)
- docs/manage-sandboxes/lifecycle.mdx
- docs/about/how-it-works.mdx
- docs/inference/tool-calling-reliability.mdx
- fern/fern.config.json
- .agents/skills/nemoclaw-user-configure-inference/SKILL.md
- .agents/skills/nemoclaw-user-configure-inference/references/tool-calling-reliability.md
- docs/get-started/quickstart.mdx
- docs/reference/troubleshooting.mdx
- .agents/skills/nemoclaw-user-reference/references/architecture.md
- docs/reference/commands-nemohermes.mdx
🚧 Files skipped from review as they are similar to previous changes (1)
- .agents/skills/nemoclaw-user-get-started/references/quickstart-hermes.md
| |---|---| | ||
| | Default | The watcher approves devices with `clientId` set to `openclaw-control-ui` or `clientMode` set to `webchat`. All other clients are rejected and logged. | | ||
| | What you can change | This is not a user-facing knob. The allowlist is defined in the entrypoint script. | | ||
| | Default | Startup auto-pairing and `connect`-time approval share one policy. NemoClaw approves devices with `clientId` set to `openclaw-control-ui` or `clientMode` set to `webchat` or `cli`, and only for `operator.pairing`, `operator.read`, and `operator.write` scopes. All other clients or scopes are rejected and logged. | |
Contributor
There was a problem hiding this comment.
Split into one sentence per line.
Line 428 contains three sentences.
The coding guidelines require one sentence per line in Markdown source to make diffs readable.
Suggested fix
-| Default | Startup auto-pairing and `connect`-time approval share one policy. NemoClaw approves devices with `clientId` set to `openclaw-control-ui` or `clientMode` set to `webchat` or `cli`, and only for `operator.pairing`, `operator.read`, and `operator.write` scopes. All other clients or scopes are rejected and logged. |
+| Default | Startup auto-pairing and `connect`-time approval share one policy.
+NemoClaw approves devices with `clientId` set to `openclaw-control-ui` or `clientMode` set to `webchat` or `cli`, and only for `operator.pairing`, `operator.read`, and `operator.write` scopes.
+All other clients or scopes are rejected and logged. |🤖 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/best-practices.md
at line 428, The Markdown table cell text beginning with "Default | Startup
auto-pairing and `connect`-time approval share one policy." contains three
sentences on one line; split it so each sentence lives on its own line in the
same table cell (e.g., one line for "Default | Startup auto-pairing and
`connect`-time approval share one policy.", one line for "NemoClaw approves
devices with `clientId` set to `openclaw-control-ui` or `clientMode` set to
`webchat` or `cli`.", and one line for "It only approves for `operator.pairing`,
`operator.read`, and `operator.write` scopes; all other clients or scopes are
rejected and logged.").
Source: Coding guidelines
| |---|---| | ||
| | Default | Enabled. The plugin registers a `before_tool_call` hook that scans for 14 high-confidence secret patterns. | | ||
| | What it covers | Three classifiers, all enforced through `isMemoryPath()`: (1) absolute `MEMORY_PATH_SEGMENTS` such as `/.openclaw/memory/`, `/.openclaw/workspace/`, `/.openclaw/agents/`, `/.openclaw/skills/`, `/.openclaw/hooks/`, `/.openclaw/credentials/`, `/.openclaw/openclaw.json`, `/.nemoclaw/`; (2) canonical workspace basenames in `MEMORY_BASENAMES` (`IDENTITY.md`, `MEMORY.md`, `SOUL.md`, `USER.md`, `AGENTS.md`) matched regardless of the surrounding path; and (3) lexically-normalized workspace-relative writes matching `MEMORY_RELATIVE_PREFIXES` (`.openclaw/`, `.nemoclaw/`, `memory/`) or named workspace daily memory paths, for embedded-fallback mode where the host's path resolver is unavailable. | | ||
| | What it covers | Three path classifiers, all enforced through `isMemoryPath()`, plus credential-shaped text such as provider API keys, OpenAI project keys with `sk-proj-` prefixes, and Slack app-level `xapp-` tokens. The path classifiers are: (1) absolute `MEMORY_PATH_SEGMENTS` such as `/.openclaw/memory/`, `/.openclaw/workspace/`, `/.openclaw/agents/`, `/.openclaw/skills/`, `/.openclaw/hooks/`, `/.openclaw/credentials/`, `/.openclaw/openclaw.json`, `/.nemoclaw/`; (2) canonical workspace basenames in `MEMORY_BASENAMES` (`IDENTITY.md`, `MEMORY.md`, `SOUL.md`, `USER.md`, `AGENTS.md`) matched regardless of the surrounding path; and (3) lexically-normalized workspace-relative writes matching `MEMORY_RELATIVE_PREFIXES` (`.openclaw/`, `.nemoclaw/`, `memory/`) or named workspace daily memory paths, for embedded-fallback mode where the host's path resolver is unavailable. | |
Contributor
There was a problem hiding this comment.
Split into one sentence per line.
Line 465 contains two sentences.
The coding guidelines require one sentence per line in Markdown source to make diffs readable.
Suggested fix
-| What it covers | Three path classifiers, all enforced through `isMemoryPath()`, plus credential-shaped text such as provider API keys, OpenAI project keys with `sk-proj-` prefixes, and Slack app-level `xapp-` tokens. The path classifiers are: (1) absolute `MEMORY_PATH_SEGMENTS` such as `/.openclaw/memory/`, `/.openclaw/workspace/`, `/.openclaw/agents/`, `/.openclaw/skills/`, `/.openclaw/hooks/`, `/.openclaw/credentials/`, `/.openclaw/openclaw.json`, `/.nemoclaw/`; (2) canonical workspace basenames in `MEMORY_BASENAMES` (`IDENTITY.md`, `MEMORY.md`, `SOUL.md`, `USER.md`, `AGENTS.md`) matched regardless of the surrounding path; and (3) lexically-normalized workspace-relative writes matching `MEMORY_RELATIVE_PREFIXES` (`.openclaw/`, `.nemoclaw/`, `memory/`) or named workspace daily memory paths, for embedded-fallback mode where the host's path resolver is unavailable. |
+| What it covers | Three path classifiers, all enforced through `isMemoryPath()`, plus credential-shaped text such as provider API keys, OpenAI project keys with `sk-proj-` prefixes, and Slack app-level `xapp-` tokens.
+The path classifiers are: (1) absolute `MEMORY_PATH_SEGMENTS` such as `/.openclaw/memory/`, `/.openclaw/workspace/`, `/.openclaw/agents/`, `/.openclaw/skills/`, `/.openclaw/hooks/`, `/.openclaw/credentials/`, `/.openclaw/openclaw.json`, `/.nemoclaw/`; (2) canonical workspace basenames in `MEMORY_BASENAMES` (`IDENTITY.md`, `MEMORY.md`, `SOUL.md`, `USER.md`, `AGENTS.md`) matched regardless of the surrounding path; and (3) lexically-normalized workspace-relative writes matching `MEMORY_RELATIVE_PREFIXES` (`.openclaw/`, `.nemoclaw/`, `memory/`) or named workspace daily memory paths, for embedded-fallback mode where the host's path resolver is unavailable. |🤖 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/best-practices.md
at line 465, The paragraph describing path classifiers and credential patterns
must be split so each sentence is on its own line; update the Markdown around
the isMemoryPath() description so the sentence about three path classifiers and
credential-shaped text is one line and the following sentence enumerating the
three classifiers (referencing MEMORY_PATH_SEGMENTS, MEMORY_BASENAMES, and
MEMORY_RELATIVE_PREFIXES) is on its own line; ensure the three classifier
categories remain intact and keep the symbol names (isMemoryPath(),
MEMORY_PATH_SEGMENTS, MEMORY_BASENAMES, MEMORY_RELATIVE_PREFIXES) unchanged for
clarity.
Source: Coding guidelines
| </AgentOnly> | ||
| If you intentionally run separate OpenShell gateways on the same host, set a different `NEMOCLAW_GATEWAY_PORT` before each onboarding run. | ||
| NemoClaw isolates the gateway name and local state by port so one port-specific gateway does not replace another. | ||
| Gateway and dashboard cleanup is scoped by sandbox name and port. |
Contributor
There was a problem hiding this comment.
Rewrite passive voice to active voice.
The phrase "Gateway and dashboard cleanup is scoped" uses passive voice. Rewrite to active voice, such as "NemoClaw scopes gateway and dashboard cleanup".
Note: This file is autogenerated from docs/manage-sandboxes/lifecycle.mdx via docs-to-skills.py. The fix should be made in the source docs/ file, not here.
🤖 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-manage-sandboxes/SKILL.md at line 116, The
sentence in the autogenerated SKILL.md uses passive voice; update the source
docs file docs/manage-sandboxes/lifecycle.mdx to use active voice (e.g., change
"Gateway and dashboard cleanup is scoped by sandbox name and port." to "NemoClaw
scopes gateway and dashboard cleanup by sandbox name and port.") and regenerate
artifacts so the change propagates into
.agents/skills/nemoclaw-user-manage-sandboxes/SKILL.md; edit the lifecycle.mdx
entry where that sentence appears and run docs-to-skills.py to produce the
updated SKILL.md.
Source: Coding guidelines
|
|
||
| - The _plugin_ is a TypeScript package that runs with OpenClaw inside the sandbox. | ||
| It registers the managed inference provider metadata, the `/nemoclaw` slash command, and runtime context hooks. | ||
| Runtime context is prepended as system guidance, so sandbox and policy instructions stay active without appearing in the visible chat transcript. |
Contributor
There was a problem hiding this comment.
Rewrite passive voice to active voice.
The phrase "Runtime context is prepended" uses passive voice. Rewrite to active voice, such as "The plugin prepends runtime context".
Note: This file is autogenerated from docs/about/how-it-works.mdx via docs-to-skills.py. The fix should be made in the source docs/ file, not here.
🤖 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/how-it-works.md at line 68,
Change the passive sentence "Runtime context is prepended as system guidance, so
sandbox and policy instructions stay active without appearing in the visible
chat transcript." in the source docs file to active voice (e.g., "The plugin
prepends runtime context as system guidance, so sandbox and policy instructions
stay active without appearing in the visible chat transcript."); make the edit
in docs/about/how-it-works.mdx (not the autogenerated .agents/... file) and keep
the rest of the sentence meaning intact.
Source: Coding guidelines
| | `NEMOCLAW_INSTALL_REF` | git ref | For internal installer commands: the git ref to install from. Overridden by the `--install-ref` flag. | | ||
| | `NEMOCLAW_INSTALL_TAG` | release tag | For internal installer commands: the release tag to install. Defaults to the admin-promoted `lkg` tag when unset. Overridden by the `--install-tag` flag. | | ||
| | `NEMOCLAW_VLLM_MODEL` | registry slug or Hugging Face model id | Selects the model the managed-vLLM install path serves. Recognised slugs: `deepseek-v4-flash`, `qwen3.6-27b`, `qwen3.6-35b-a3b-nvfp4`, `nemotron-3-nano-4b`, `deepseek-r1-distill-70b`. Unset uses the per-platform profile default. Gated models (e.g. `deepseek-r1-distill-70b`) require `HF_TOKEN` or `HUGGING_FACE_HUB_TOKEN`. | | ||
| | `NEMOCLAW_MINIMAL_BOOTSTRAP` | `1` to enable | Skips default OpenClaw workspace-template seeding for new pristine workspaces. Existing files are not deleted; see [Runtime Controls](../manage-sandboxes/runtime-controls). | |
Contributor
There was a problem hiding this comment.
Rewrite passive voice to active voice.
The phrase "Existing files are not deleted" uses passive voice. Rewrite to active voice.
Suggested rewrite
-| `NEMOCLAW_MINIMAL_BOOTSTRAP` | `1` to enable | Skips default OpenClaw workspace-template seeding for new pristine workspaces. Existing files are not deleted; see [Runtime Controls](../manage-sandboxes/runtime-controls). |
+| `NEMOCLAW_MINIMAL_BOOTSTRAP` | `1` to enable | Skips default OpenClaw workspace-template seeding for new pristine workspaces. NemoClaw does not delete existing files; see [Runtime Controls](../manage-sandboxes/runtime-controls). |📝 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
| | `NEMOCLAW_MINIMAL_BOOTSTRAP` | `1` to enable | Skips default OpenClaw workspace-template seeding for new pristine workspaces. Existing files are not deleted; see [Runtime Controls](../manage-sandboxes/runtime-controls). | | |
| | `NEMOCLAW_MINIMAL_BOOTSTRAP` | `1` to enable | Skips default OpenClaw workspace-template seeding for new pristine workspaces. NemoClaw does not delete existing files; see [Runtime Controls](../manage-sandboxes/runtime-controls). | |
🤖 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/reference/commands.mdx` at line 1819, Update the passive phrase in the
table row for NEMOCLAW_MINIMAL_BOOTSTRAP so it uses active voice: replace
"Existing files are not deleted" with an active construction such as "This
setting does not delete existing files" (or "It does not delete existing files")
in the description cell for NEMOCLAW_MINIMAL_BOOTSTRAP to convey the same
meaning in active voice.
Source: Coding guidelines
| |---|---| | ||
| | Default | The watcher approves devices with `clientId` set to `openclaw-control-ui` or `clientMode` set to `webchat`. All other clients are rejected and logged. | | ||
| | What you can change | This is not a user-facing knob. The allowlist is defined in the entrypoint script. | | ||
| | Default | Startup auto-pairing and `connect`-time approval share one policy. NemoClaw approves devices with `clientId` set to `openclaw-control-ui` or `clientMode` set to `webchat` or `cli`, and only for `operator.pairing`, `operator.read`, and `operator.write` scopes. All other clients or scopes are rejected and logged. | |
Contributor
There was a problem hiding this comment.
Split into one sentence per line.
Line 453 contains three sentences.
As per coding guidelines, Markdown source should use one sentence per line to make diffs readable.
Suggested fix
-| Default | Startup auto-pairing and `connect`-time approval share one policy. NemoClaw approves devices with `clientId` set to `openclaw-control-ui` or `clientMode` set to `webchat` or `cli`, and only for `operator.pairing`, `operator.read`, and `operator.write` scopes. All other clients or scopes are rejected and logged. |
+| Default | Startup auto-pairing and `connect`-time approval share one policy.
+NemoClaw approves devices with `clientId` set to `openclaw-control-ui` or `clientMode` set to `webchat` or `cli`, and only for `operator.pairing`, `operator.read`, and `operator.write` scopes.
+All other clients or scopes are rejected and logged. |🤖 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/best-practices.mdx` at line 453, The table cell containing
"Default | Startup auto-pairing and `connect`-time approval share one policy.
NemoClaw approves devices with `clientId` set to `openclaw-control-ui` or
`clientMode` set to `webchat` or `cli`, and only for `operator.pairing`,
`operator.read`, and `operator.write` scopes. All other clients or scopes are
rejected and logged." should be split so each sentence is on its own source
line; edit the table row (the cell after the first pipe) so the three sentences
appear on three separate lines (keeping the leading "Default |" and any required
pipe separators intact) — ensure you preserve escaping/backticks and punctuation
exactly while breaking the single-line cell into three lines.
Source: Coding guidelines
| |---|---| | ||
| | Default | Enabled. The plugin registers a `before_tool_call` hook that scans for 14 high-confidence secret patterns. | | ||
| | What it covers | Three classifiers, all enforced through `isMemoryPath()`: (1) absolute `MEMORY_PATH_SEGMENTS` such as `/.openclaw/memory/`, `/.openclaw/workspace/`, `/.openclaw/agents/`, `/.openclaw/skills/`, `/.openclaw/hooks/`, `/.openclaw/credentials/`, `/.openclaw/openclaw.json`, `/.nemoclaw/`; (2) canonical workspace basenames in `MEMORY_BASENAMES` (`IDENTITY.md`, `MEMORY.md`, `SOUL.md`, `USER.md`, `AGENTS.md`) matched regardless of the surrounding path; and (3) lexically-normalized workspace-relative writes matching `MEMORY_RELATIVE_PREFIXES` (`.openclaw/`, `.nemoclaw/`, `memory/`) or named workspace daily memory paths, for embedded-fallback mode where the host's path resolver is unavailable. | | ||
| | What it covers | Three path classifiers, all enforced through `isMemoryPath()`, plus credential-shaped text such as provider API keys, OpenAI project keys with `sk-proj-` prefixes, and Slack app-level `xapp-` tokens. The path classifiers are: (1) absolute `MEMORY_PATH_SEGMENTS` such as `/.openclaw/memory/`, `/.openclaw/workspace/`, `/.openclaw/agents/`, `/.openclaw/skills/`, `/.openclaw/hooks/`, `/.openclaw/credentials/`, `/.openclaw/openclaw.json`, `/.nemoclaw/`; (2) canonical workspace basenames in `MEMORY_BASENAMES` (`IDENTITY.md`, `MEMORY.md`, `SOUL.md`, `USER.md`, `AGENTS.md`) matched regardless of the surrounding path; and (3) lexically-normalized workspace-relative writes matching `MEMORY_RELATIVE_PREFIXES` (`.openclaw/`, `.nemoclaw/`, `memory/`) or named workspace daily memory paths, for embedded-fallback mode where the host's path resolver is unavailable. | |
Contributor
There was a problem hiding this comment.
Split into one sentence per line.
Line 490 contains two sentences.
As per coding guidelines, Markdown source should use one sentence per line to make diffs readable.
Suggested fix
-| What it covers | Three path classifiers, all enforced through `isMemoryPath()`, plus credential-shaped text such as provider API keys, OpenAI project keys with `sk-proj-` prefixes, and Slack app-level `xapp-` tokens. The path classifiers are: (1) absolute `MEMORY_PATH_SEGMENTS` such as `/.openclaw/memory/`, `/.openclaw/workspace/`, `/.openclaw/agents/`, `/.openclaw/skills/`, `/.openclaw/hooks/`, `/.openclaw/credentials/`, `/.openclaw/openclaw.json`, `/.nemoclaw/`; (2) canonical workspace basenames in `MEMORY_BASENAMES` (`IDENTITY.md`, `MEMORY.md`, `SOUL.md`, `USER.md`, `AGENTS.md`) matched regardless of the surrounding path; and (3) lexically-normalized workspace-relative writes matching `MEMORY_RELATIVE_PREFIXES` (`.openclaw/`, `.nemoclaw/`, `memory/`) or named workspace daily memory paths, for embedded-fallback mode where the host's path resolver is unavailable. |
+| What it covers | Three path classifiers, all enforced through `isMemoryPath()`, plus credential-shaped text such as provider API keys, OpenAI project keys with `sk-proj-` prefixes, and Slack app-level `xapp-` tokens.
+The path classifiers are: (1) absolute `MEMORY_PATH_SEGMENTS` such as `/.openclaw/memory/`, `/.openclaw/workspace/`, `/.openclaw/agents/`, `/.openclaw/skills/`, `/.openclaw/hooks/`, `/.openclaw/credentials/`, `/.openclaw/openclaw.json`, `/.nemoclaw/`; (2) canonical workspace basenames in `MEMORY_BASENAMES` (`IDENTITY.md`, `MEMORY.md`, `SOUL.md`, `USER.md`, `AGENTS.md`) matched regardless of the surrounding path; and (3) lexically-normalized workspace-relative writes matching `MEMORY_RELATIVE_PREFIXES` (`.openclaw/`, `.nemoclaw/`, `memory/`) or named workspace daily memory paths, for embedded-fallback mode where the host's path resolver is unavailable. |🤖 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/best-practices.mdx` at line 490, The paragraph on memory path
classifiers is two sentences and needs to be split so each sentence is on its
own Markdown line; edit the line containing the descriptions of isMemoryPath(),
MEMORY_PATH_SEGMENTS, MEMORY_BASENAMES, and MEMORY_RELATIVE_PREFIXES so that
each sentence becomes a separate line (i.e., break after the first sentence
describing what it covers and then break the long sentence that lists the three
classifiers into its own line), preserving the exact identifiers and examples
(`isMemoryPath()`, `MEMORY_PATH_SEGMENTS`, `MEMORY_BASENAMES`,
`MEMORY_RELATIVE_PREFIXES`, and the example paths/basenames).
Source: Coding guidelines
cv
approved these changes
Jun 6, 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
v0.0.60section todocs/about/release-notes.mdxusing the dev announcement from discussion NemoClaw v0.0.60 is out #4877..agents/skills/from the current Fern docs output and upgrades Fern from5.44.3to5.45.0.Source summary
docs/reference/architecture.mdx,docs/about/how-it-works.mdx,docs/about/release-notes.mdx: Documents system-only runtime context that stays out of visible chat.docs/reference/architecture.mdx,docs/about/how-it-works.mdx,docs/about/release-notes.mdx: Documents try-first sandbox network/filesystem guidance and clearer failure classification.docs/security/best-practices.mdx,docs/about/release-notes.mdx: Documents shared OpenClaw device-approval policy for startup and connect.docs/reference/network-policies.mdx,docs/network-policy/integration-policy-examples.mdx,docs/get-started/quickstart.mdx,docs/get-started/quickstart-hermes.mdx,docs/reference/commands.mdx: Documentsweather,public-reference, and Hermes managed-tool gateway preset behavior.docs/reference/network-policies.mdx,docs/reference/commands.mdx: Documents non-interactive policy-tier fail-fast behavior and interactive prompt fallback.docs/reference/commands.mdx: Documents env-aware default sandbox resolution forlist,status, andtunnelcommands.docs/reference/commands.mdx: Documents$$nemoclaw tunnel statusbehavior.docs/reference/commands.mdx: Documents line-scoped policy preset descriptions inpolicy-list.docs/reference/architecture.mdx: Documents package-managed OpenShell gateway service and Docker-driver gateway-marker behavior.docs/manage-sandboxes/lifecycle.mdx: Documents concurrent gateway/dashboard cleanup isolation by sandbox name and port.docs/reference/troubleshooting.mdx: Documents Docker GPU patch rollback behavior.docs/reference/troubleshooting.mdx,docs/reference/commands.mdx: Keeps mutable OpenClaw config permission guidance aligned and removes skipped experimental wording.docs/reference/commands.mdx: Keeps.dockerignorehandling for customonboard --from <Dockerfile>contexts in generated skills.docs/reference/commands.mdx,docs/manage-sandboxes/runtime-controls.mdx: DocumentsNEMOCLAW_MINIMAL_BOOTSTRAPand generated skill coverage.docs/inference/inference-options.mdx,docs/reference/troubleshooting.mdx: Documents local NVIDIA NIM platform-digest pulls and served-model id adoption.docs/inference/inference-options.mdx: Documents stable NGC managed-vLLM image lineage and DGX Station DeepSeek V4 Flash coverage.docs/inference/use-local-inference.mdx,docs/reference/troubleshooting.mdx: Documents Ollama model fit filtering, 16K context floor, cold-load retry, and failed-model exclusion.docs/inference/switch-inference-providers.mdx: Documents API-family sync, Hermesapi_mode, and Bedrock Runtime exception.docs/inference/tool-calling-reliability.mdx: Documents Nemotron managed-inference native tool-search fallback.docs/inference/switch-inference-providers.mdx: Documents interactive multimodal input prompting.docs/reference/troubleshooting.mdx: Keeps proxy bypass normalization in generated troubleshooting coverage.docs/get-started/quickstart-hermes.mdx: Documents prebuilt Hermes dashboard assets and TUI recovery without runtime rebuilds.docs/inference/switch-inference-providers.mdx,docs/reference/commands.mdx: Documents Hermes proxy API-key placeholder preservation during inference switches.docs/manage-sandboxes/messaging-channels.mdx,.agents/skills/: Keeps messaging enrollment behavior aligned with manifest-hook implementation.docs/security/best-practices.mdx,docs/security/credential-storage.mdx: Documents Hermes placeholder-only secret boundary for sandbox-visible runtime files.docs/security/best-practices.mdx,docs/about/release-notes.mdx: Documents expanded memory scanner examples for OpenAI project keys and Slack app-level tokens.docs/reference/commands.mdx: Documents OpenClaw skill install mirroring into the agent home directory.docs/about/release-notes.mdx: Uses the prior release-prep structure and generated.agents/skills/refresh as the template for this release.Verification
python3 scripts/docs-to-skills.py docs/ .agents/skills/ --prefix nemoclaw-user --doc-platform fern-mdxpython3 scripts/docs-to-skills.py docs/ .agents/skills/ skills/ --prefix nemoclaw-user --doc-platform fern-mdx --dry-runnpm run docsgit diff --checkdocs/,.agents/skills/, andskills/npm run build:clinpm run typecheck:cliSummary by CodeRabbit
Release Notes
New Features
Bug Fixes
Documentation