docs: refresh 0.0.54 release docs#4539
Merged
Merged
Conversation
miyoungc
added
documentation
Contributor
📝 WalkthroughWalkthroughThis PR updates NemoClaw documentation across 16 files to reflect v0.0.54 changes: Windows/WSL Docker Desktop integration for Ollama, optional Hermes native web dashboard with new environment variables, clarified onboarding flow sequencing with web search/messaging before policy tier selection, GPU memory cleanup Ollama behavior, messaging channel bridge validation, sandbox filesystem security, Homebrew guidance, release notes, and a Fern config bump. ChangesCore Windows/WSL, Ollama, and Hermes Feature Documentation
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
ESLint skipped: no ESLint configuration detected in root package.json. To enable, add Comment |
Contributor
|
🌿 Preview your docs: https://nvidia-preview-pr-4539.docs.buildwithfern.com/nemoclaw |
Contributor
E2E Advisor RecommendationRequired E2E: None Full advisor summaryE2E Recommendation AdvisorBase: Required E2E
Optional E2E
New E2E recommendations
|
Contributor
E2E Scenario Advisor RecommendationRequired scenario E2E: None Full scenario advisor summaryE2E Scenario AdvisorBase: Required scenario E2E
Optional scenario E2E
Relevant changed files
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 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-deploy-remote/references/sandbox-hardening.md:
- Around line 88-94: The change was made directly in the autogenerated skill
markdown
`.agents/skills/nemoclaw-user-deploy-remote/references/sandbox-hardening.md`;
revert that edit and instead apply the modification to the canonical docs source
under the docs/ tree (the source page that generates the sandbox-hardening.md
content), then run the docs-to-skills regeneration pipeline so the updated text
flows into `.agents/skills/nemoclaw-user-*`; do not edit files under
`.agents/skills/nemoclaw-user-*` directly as per the guidelines.
In
@.agents/skills/nemoclaw-user-manage-policy/references/integration-policy-examples.md:
- Around line 264-266: This change edits an autogenerated skill markdown
(.agents/skills/nemoclaw-user-*/*.md) which must not be modified directly;
revert any edits to
".agents/skills/nemoclaw-user-manage-policy/references/integration-policy-examples.md"
and instead make the desired content change in the canonical docs source used to
generate these files, then run the docs/skill generation flow (the doc source ->
generation script) to regenerate the .agents/skills/nemoclaw-user-*/*.md outputs
and commit those generated changes; ensure the CI/regeneration step creates the
updated integration-policy-examples.md rather than editing it manually.
In @.agents/skills/nemoclaw-user-overview/references/release-notes.md:
- Around line 7-18: The release-notes.md under the autogenerated skill path
(.agents/skills/nemoclaw-user-overview/references/release-notes.md) was edited
by hand but must be regenerated from the skill generator; revert the manual
changes, restore the file to the generated state from the generator output, and
re-run the skill generation pipeline that produces nemoClaw user overview skills
(the generator responsible for .agents/skills/nemoclaw-user-*/*.md) so the file
is recreated correctly; if the generator source templates changed, update those
templates instead of editing this markdown directly and commit the regenerated
artifact.
In `@docs/reference/commands.mdx`:
- Line 705: The sentence in docs/reference/commands.mdx uses passive voice ("a
rebuild triggered by `channels add`"); rewrite it in active voice so the subject
performs the action, e.g., start the sentence with the command `channels add` as
the actor (for example: "`channels add` triggers a rebuild for Telegram,
Discord, and Slack that also verifies the selected bridge and reports
credential, startup, or plugin discovery warnings"), ensuring you reference the
`channels add` command and preserve the original checks (selected bridge
verification and credential/startup/plugin discovery warnings) and phrasing
consistent with docs/manage-sandboxes/messaging-channels.mdx.
🪄 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: 3a348c05-cc45-4bdc-be5f-b0057ba3db0a
📒 Files selected for processing (18)
.agents/skills/nemoclaw-user-configure-inference/SKILL.md.agents/skills/nemoclaw-user-configure-inference/references/use-local-inference-details.md.agents/skills/nemoclaw-user-deploy-remote/references/sandbox-hardening.md.agents/skills/nemoclaw-user-get-started/SKILL.md.agents/skills/nemoclaw-user-get-started/references/quickstart-details.md.agents/skills/nemoclaw-user-get-started/references/quickstart-hermes.md.agents/skills/nemoclaw-user-get-started/references/windows-preparation.md.agents/skills/nemoclaw-user-manage-policy/references/integration-policy-examples.md.agents/skills/nemoclaw-user-manage-sandboxes/references/messaging-channels.md.agents/skills/nemoclaw-user-overview/references/release-notes.md.agents/skills/nemoclaw-user-reference/references/commands.md.agents/skills/nemoclaw-user-reference/references/troubleshooting.mddocs/about/release-notes.mdxdocs/get-started/windows-preparation.mdxdocs/inference/use-local-inference.mdxdocs/manage-sandboxes/messaging-channels.mdxdocs/reference/commands.mdxfern/fern.config.json
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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-contributor-update-docs/SKILL.md:
- Line 137: The release-note bullet in SKILL.md uses a placeholder link
`/doc/path` which breaks link checks; update the line "For more information,
refer to [DOC PAGE](/doc/path)." to use a real doc path (for example the v0.0.54
release page) such as "For more information, refer to [Release
v0.0.54](/docs/releases/v0.0.54)." or, if you must keep an example, escape it so
the link checker ignores it; locate that exact sentence in SKILL.md and replace
the placeholder link accordingly.
🪄 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: 28a4a241-d8b0-40a3-895d-b5159b0b6acd
📒 Files selected for processing (3)
.agents/skills/nemoclaw-contributor-update-docs/SKILL.md.agents/skills/nemoclaw-user-overview/references/release-notes.mddocs/about/release-notes.mdx
✅ Files skipped from review due to trivial changes (2)
- docs/about/release-notes.mdx
- .agents/skills/nemoclaw-user-overview/references/release-notes.md
|
|
||
| **Release prep only:** When updating `docs/about/release-notes.mdx`: | ||
|
|
||
| - For each release-note bullet that corresponds to a deeper doc page, end the bullet with `For more information, refer to [DOC PAGE](/doc/path).` |
Contributor
There was a problem hiding this comment.
Replace the placeholder path with a concrete example to fix the broken link.
The placeholder /doc/path is causing the link checker to fail. Use a real example from the release notes instead to demonstrate the pattern and fix the pipeline failure.
🔧 Proposed fix using a concrete example from v0.0.54 release notes
-- For each release-note bullet that corresponds to a deeper doc page, end the bullet with `For more information, refer to [DOC PAGE](/doc/path).`
+- For each release-note bullet that corresponds to a deeper doc page, end the bullet with `For more information, refer to [DOC PAGE](/doc/path).` For example: `For more information, refer to [Messaging Channels](/manage-sandboxes/messaging-channels).`Alternatively, escape the example so the link checker ignores it:
-- For each release-note bullet that corresponds to a deeper doc page, end the bullet with `For more information, refer to [DOC PAGE](/doc/path).`
+- For each release-note bullet that corresponds to a deeper doc page, end the bullet with: `For more information, refer to [DOC PAGE](/doc/path).`🧰 Tools
🪛 GitHub Actions: Docs / Link Check / 0_markdown-links.txt
[error] 137-137: check-docs.sh (links) failed: broken site route in .agents/skills/nemoclaw-contributor-update-docs/SKILL.md:137 -> /doc/path
🪛 GitHub Actions: Docs / Link Check / markdown-links
[error] 137-137: check-docs.sh (links) failed: broken site route/target link in .agents/skills/nemoclaw-contributor-update-docs/SKILL.md:137 -> /doc/path
🤖 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 at line 137, The
release-note bullet in SKILL.md uses a placeholder link `/doc/path` which breaks
link checks; update the line "For more information, refer to [DOC
PAGE](/doc/path)." to use a real doc path (for example the v0.0.54 release page)
such as "For more information, refer to [Release
v0.0.54](/docs/releases/v0.0.54)." or, if you must keep an example, escape it so
the link checker ignores it; locate that exact sentence in SKILL.md and replace
the placeholder link accordingly.
Contributor
PR Review AdvisorFindings: 1 needs attention, 1 worth checking, 0 nice ideas Review findings🛠️ Needs attention
🔎 Worth checking
🌱 Nice ideas
Since last review detailsCurrent findings:
This is an automated advisory review. A human maintainer must make the final merge decision. |
cv
approved these changes
May 29, 2026
This was referenced May 29, 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
Refreshes the NemoClaw documentation for the v0.0.54 release and regenerates user skills from the Fern MDX source. Also keeps the Fern CLI pin current so local docs checks use the upgraded Fern version.
Related Issue
Changes
docs/manage-sandboxes/messaging-channels.mdx,docs/reference/commands.mdx,docs/about/release-notes.mdx: Document Telegram, Discord, and Slack post-rebuild bridge verification and summarize channel activation fixes.docs/about/release-notes.mdx: Include Slack generated channel enablement in the v0.0.54 messaging summary.docs/get-started/windows-preparation.mdx,docs/about/release-notes.mdx: Document safer Windows bootstrap behavior for Ubuntu first-run and Docker Desktop WSL integration.docs/inference/use-local-inference.mdx,docs/about/release-notes.mdx: Document the Docker Desktop WSL requirement for Windows-host Ollama.docs/about/release-notes.mdx: Summarize the optional NemoHermes native web dashboard and related environment variables.docs/about/release-notes.mdx: Summarize copy-paste recovery hints for invalid sandbox names and missing NVIDIA API keys.docs/about/release-notes.mdx: Summarize the Linuxbrew prefix fix for sandbox Homebrew usage.docs/about/release-notes.mdx: Summarize/nemoclawslash command startup activation.docs/about/release-notes.mdx: Summarize scope-upgrade approval recovery.docs/about/release-notes.mdx: Summarize the narrowedweb_fetchhost-gateway allowance.docs/about/release-notes.mdx: Summarize Hermes Provider smoke-check behavior for OAuth versus Nous API key setup..agents/skills/nemoclaw-user-*references fromdocs/and updatefern/fern.config.jsonto Fern5.41.2.Type of Change
Verification
npx prek run --all-filespassesnpm testpassesnpm run docsbuilds without warnings (doc changes only)Signed-off-by: Miyoung Choi miyoungc@nvidia.com
Summary by CodeRabbit
New Features
Bug Fixes
Documentation