Skip to content

docs: refresh 0.0.56 release documentation#4618

Merged
miyoungc merged 4 commits into
mainfrom
docs/v0.0.56-release-docs
Jun 1, 2026
Merged

docs: refresh 0.0.56 release documentation#4618
miyoungc merged 4 commits into
mainfrom
docs/v0.0.56-release-docs

Conversation

@miyoungc
Copy link
Copy Markdown
Collaborator

@miyoungc miyoungc commented Jun 1, 2026

Summary

  • Adds the v0.0.56 release notes section with links to the deeper docs pages for installer, status, inference, messaging, policy, and lifecycle changes.
  • Updates source docs for the remaining release-prep gaps around uv in the PyPI preset, compact WhatsApp pairing guidance, and nemoclaw inference set command boundaries.
  • Refreshes generated nemoclaw-user-* skills and removes skipped experimental command terms from generated skill surfaces.

Source summary

Verification

  • python3 scripts/docs-to-skills.py docs/ .agents/skills/ --prefix nemoclaw-user --doc-platform fern-mdx
  • npm run docs (passes; Fern reports the pre-existing light-mode accent contrast warning)
  • rg "permissive mode|shields down|shields up|shields status|config rotate-token|rotate-token" .agents/skills (no matches)
  • npm run build:cli (run to refresh local CLI artifacts for the pre-push TypeScript hook)
  • Commit hooks passed, including NEMOCLAW_* env-var documentation gate, Verify docs-to-skills output, markdownlint-cli2, gitleaks, and Test (skills YAML).

Summary by CodeRabbit

  • Documentation

    • Expanded Model Router setup (examples, flow diagram, credential handling); strengthened agent-config immutability and integrity guidance; updated messaging channels (Telegram aliases, WhatsApp pairing/diagnostics); extensive CLI docs revisions (GPU detection, inference set behavior, uninstall/rebuild preservation); rebranded overview and added v0.0.56 release notes.
  • New Features

    • Added messaging diagnostics command (channels status with JSON), skill remove docs; Hermes unflagged as experimental; DGX Spark quickstart sandbox-name note.

@miyoungc miyoungc added documentation Improvements or additions to documentation v0.0.56 Release target labels Jun 1, 2026
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 1, 2026

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 989e92fe-58ae-47c9-9068-8b3d9de5480e

📥 Commits

Reviewing files that changed from the base of the PR and between b5731b2 and a119907.

📒 Files selected for processing (3)
  • .agents/skills/nemoclaw-user-overview/references/overview.md
  • .agents/skills/nemoclaw-user-overview/references/release-notes.md
  • docs/about/overview.mdx
✅ Files skipped from review due to trivial changes (3)
  • docs/about/overview.mdx
  • .agents/skills/nemoclaw-user-overview/references/release-notes.md
  • .agents/skills/nemoclaw-user-overview/references/overview.md

📝 Walkthrough

Walkthrough

Documentation-only PR updating NemoClaw v0.0.56 references: model router configuration, host immutability/security guidance, NemoClaw positioning, sandbox lifecycle and messaging, expanded CLI command docs, integration/policy entries, and release notes across skill and public MDX files.

Changes

v0.0.56 Documentation Updates

Layer / File(s) Summary
Model Router setup and inference configuration
.agents/skills/nemoclaw-user-configure-inference/references/inference-options.md
Pool config edit instructions, YAML router example, tolerance behavior table, host-vs-sandbox runtime clarification, end-to-end request flow diagram, and credentials-flow note.
Security immutability workflow documentation
.agents/skills/nemoclaw-user-configure-security/references/best-practices.md, docs/security/best-practices.mdx
Host-side immutability workflow: locked high-risk and secret directories with specified ownership/modes, gateway read exemptions, union-based lock inventory, runtime exemptions, session permission restoration, symlink refusal behavior, and content integrity seal/hash verification.
NemoClaw brand and positioning
.agents/skills/nemoclaw-user-overview/SKILL.md, .agents/skills/nemoclaw-user-overview/references/overview.md, .agents/skills/nemoclaw-user-overview/references/how-it-works.md, .agents/skills/nemoclaw-user-get-started/references/quickstart-hermes.md
Reframed wording from OpenClaw-specific language to NemoClaw/agent operations; overview and use cases updated; Hermes quickstart adjusted and experimental notice removed.
Sandbox lifecycle and messaging/management docs
.agents/skills/nemoclaw-user-manage-sandboxes/SKILL.md, .agents/skills/nemoclaw-user-manage-sandboxes/references/messaging-channels.md, .agents/skills/nemoclaw-user-reference/references/troubleshooting.md, docs/manage-sandboxes/messaging-channels.mdx
Maintained/lkg release guidance, OpenShell gateway cleanup and pkill steps, uninstall user-data preservation and env override, DGX Spark sandbox-name note, Telegram allowlist aliases and e2e test guidance, WhatsApp pairing/connect diagnostics, and k3s image remediation.
CLI commands reference expansions
.agents/skills/nemoclaw-user-reference/references/commands.md, docs/reference/commands.mdx
Onboard --fresh behavior, prepared OpenShell removal steps, expanded GPU passthrough detection including Jetson/Tegra fallbacks, connect/status/channels status/skill remove/rebuild docs, GPU-mode preservation across rebuilds, inference set provider+model sync semantics, debug tarball atomic-write behavior, uninstall preservation matrix, and new env vars (NEMOCLAW_INSTALL_TAG, NEMOCLAW_SKIP_SLACK_AUTH_VALIDATION, NEMOCLAW_SHIELDS_ACCEPT_LEGACY_BASELINE).
Policy and integration documentation
.agents/skills/nemoclaw-user-manage-policy/references/integration-policy-examples.md, docs/network-policy/integration-policy-examples.mdx
Jira preset validation changed to a body-visible API probe, PyPI preset row added and expanded to list allowed Python/uv entry points and custom-path guidance, and Telegram DM troubleshooting with allowlist and e2e markers.
Release notes and public MDX updates
.agents/skills/nemoclaw-user-overview/references/release-notes.md, .agents/skills/nemoclaw-user-manage-sandboxes/evals/evals.json, docs/about/release-notes.mdx, docs/manage-sandboxes/messaging-channels.mdx, docs/security/best-practices.mdx
Added v0.0.56 release notes, updated public MDX intro and release notes, aligned messaging-channel pairing docs, condensed/rewrote security best-practices immutability and content-seal language, and adjusted an eval fixture question string.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

  • NVIDIA/NemoClaw#3067: Related docs-to-skills generation work touching similar skill markdown outputs.
  • NVIDIA/NemoClaw#4155: Related host immutability/state-dir lock behavior and preflight locking implementation.
  • NVIDIA/NemoClaw#3151: Previously updated Model Router and content-integrity docs overlapping these changes.

Suggested reviewers

  • ericksoa
  • cv

"🐰 Release notes hop with v0.0.56 delight,
Model routers choose with tolerance and might,
Locks guard state with root-set keys,
Messaging and CLI clearer to read,
NemoClaw documents gleam in the light."

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and accurately summarizes the main objective of this pull request: updating documentation for the v0.0.56 release. It is concise, specific, and directly reflects the substantial documentation refresh across release notes, CLI commands, policy guides, and skill documentation.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/v0.0.56-release-docs

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 1, 2026

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 1, 2026

E2E Advisor Recommendation

Required E2E: None
Optional E2E: None

Workflow run

Full advisor summary

E2E Recommendation Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required E2E

  • None. No E2E is recommended. This PR changes documentation, agent skill reference content, and a skill eval prompt only. It does not touch installer/onboarding code, sandbox lifecycle code, credential handling, security enforcement, network-policy YAML assets, inference routing implementation, deployment automation, or runtime assistant flows. Docs/skill validation should be handled by the existing docs and skills CI rather than sandbox E2E.

Optional E2E

  • None.

New E2E recommendations

  • None.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 1, 2026

E2E Scenario Advisor Recommendation

Required scenario E2E: None
Optional scenario E2E: None

Workflow run

Full scenario advisor summary

E2E Scenario Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required scenario E2E

  • None. Changes are limited to documentation, agent-skill reference content, and agent-skill eval metadata outside test/e2e-scenario and the scenario workflows. They do not affect scenario E2E runtime, scenario metadata, expected-state contracts, suite definitions, suite scripts, onboarding helpers, or dispatchable scenario behavior.

Optional scenario E2E

  • None.

Relevant changed files

  • None.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 1, 2026

PR Review Advisor

Findings: 0 needs attention, 4 worth checking, 0 nice ideas
Since last review: 0 prior items resolved, 2 still apply, 0 new items found

Review findings

🛠️ Needs attention

  • None.

🔎 Worth checking

  • Source-of-truth review needed: Jira manual curl validation guidance: The advisor marked localized patch analysis as needs_followup.
    • Recommendation: Identify the invalid state, source boundary, source-fix constraint, regression test, and removal condition before merging the localized behavior.
    • Evidence: Covered by the Jira finding: `docs/network-policy/integration-policy-examples.mdx` instructs explicitly approving `curl` for `api.atlassian.com` after stating the preset does not allow `curl`.
  • Source-of-truth review needed: Manual gateway retirement recovery command: The advisor marked localized patch analysis as needs_followup.
    • Recommendation: Identify the invalid state, source boundary, source-fix constraint, regression test, and removal condition before merging the localized behavior.
    • Evidence: Covered by the gateway-retirement finding: `docs/reference/commands.mdx`, `docs/manage-sandboxes/lifecycle.mdx`, and the generated skill copy retain `sudo pkill -f openshell-gateway`.
  • Jira validation guidance can leave a broader curl egress approval than the preset intends (docs/network-policy/integration-policy-examples.mdx:225): The updated Jira section says the maintained `jira` preset intentionally allows Node.js and does not allow `curl`, but then instructs operators to explicitly approve `curl` for `api.atlassian.com` in OpenShell as the manual success path. OpenShell approvals persist as durable policy revisions, so following this validation literally can leave a sandbox with curl-based Atlassian egress after the check, weakening the preset's binary-scoped least-privilege boundary.
    • Recommendation: Prefer a validation path that stays within the maintained preset, or add explicit cleanup/reset instructions immediately after the curl approval step, such as removing the temporary approval or using a throwaway validation sandbox. Mirror the fix in the generated skill copy.
    • Evidence: `docs/network-policy/integration-policy-examples.mdx` says the preset intentionally does not allow `curl`, then says: "After explicitly approving curl for `api.atlassian.com` in OpenShell, it should return Atlassian's unauthenticated `401` JSON response." The generated `.agents/skills/nemoclaw-user-manage-policy/references/integration-policy-examples.md` contains the same guidance.
  • Gateway retirement docs use a broad privileged process kill (docs/reference/commands.mdx:97): The manual OpenShell upgrade-retirement guidance tells users to run `sudo pkill -f openshell-gateway` if a privileged host gateway remains. There is no untrusted interpolation, but the pattern match is broad and can stop unrelated OpenShell gateways or processes on a shared host, creating avoidable availability and operational-safety risk.
    • Recommendation: Scope the recovery command to the specific gateway service, PID, container, or gateway name when possible. If a broad `pkill` remains as a last resort, make the blast radius explicit and tell operators to inspect matching processes first. Mirror the wording in `docs/manage-sandboxes/lifecycle.mdx` and the generated skill docs.
    • Evidence: `docs/reference/commands.mdx` says to "stop any remaining privileged host gateway with `sudo pkill -f openshell-gateway`"; `docs/manage-sandboxes/lifecycle.mdx` and `.agents/skills/nemoclaw-user-manage-sandboxes/SKILL.md` contain matching guidance.

🌱 Nice ideas

  • None.
Since last review details

Current findings:

  • Source-of-truth review needed: Jira manual curl validation guidance: The advisor marked localized patch analysis as needs_followup.
    • Recommendation: Identify the invalid state, source boundary, source-fix constraint, regression test, and removal condition before merging the localized behavior.
    • Evidence: Covered by the Jira finding: `docs/network-policy/integration-policy-examples.mdx` instructs explicitly approving `curl` for `api.atlassian.com` after stating the preset does not allow `curl`.
  • Source-of-truth review needed: Manual gateway retirement recovery command: The advisor marked localized patch analysis as needs_followup.
    • Recommendation: Identify the invalid state, source boundary, source-fix constraint, regression test, and removal condition before merging the localized behavior.
    • Evidence: Covered by the gateway-retirement finding: `docs/reference/commands.mdx`, `docs/manage-sandboxes/lifecycle.mdx`, and the generated skill copy retain `sudo pkill -f openshell-gateway`.
  • Jira validation guidance can leave a broader curl egress approval than the preset intends (docs/network-policy/integration-policy-examples.mdx:225): The updated Jira section says the maintained `jira` preset intentionally allows Node.js and does not allow `curl`, but then instructs operators to explicitly approve `curl` for `api.atlassian.com` in OpenShell as the manual success path. OpenShell approvals persist as durable policy revisions, so following this validation literally can leave a sandbox with curl-based Atlassian egress after the check, weakening the preset's binary-scoped least-privilege boundary.
    • Recommendation: Prefer a validation path that stays within the maintained preset, or add explicit cleanup/reset instructions immediately after the curl approval step, such as removing the temporary approval or using a throwaway validation sandbox. Mirror the fix in the generated skill copy.
    • Evidence: `docs/network-policy/integration-policy-examples.mdx` says the preset intentionally does not allow `curl`, then says: "After explicitly approving curl for `api.atlassian.com` in OpenShell, it should return Atlassian's unauthenticated `401` JSON response." The generated `.agents/skills/nemoclaw-user-manage-policy/references/integration-policy-examples.md` contains the same guidance.
  • Gateway retirement docs use a broad privileged process kill (docs/reference/commands.mdx:97): The manual OpenShell upgrade-retirement guidance tells users to run `sudo pkill -f openshell-gateway` if a privileged host gateway remains. There is no untrusted interpolation, but the pattern match is broad and can stop unrelated OpenShell gateways or processes on a shared host, creating avoidable availability and operational-safety risk.
    • Recommendation: Scope the recovery command to the specific gateway service, PID, container, or gateway name when possible. If a broad `pkill` remains as a last resort, make the blast radius explicit and tell operators to inspect matching processes first. Mirror the wording in `docs/manage-sandboxes/lifecycle.mdx` and the generated skill docs.
    • Evidence: `docs/reference/commands.mdx` says to "stop any remaining privileged host gateway with `sudo pkill -f openshell-gateway`"; `docs/manage-sandboxes/lifecycle.mdx` and `.agents/skills/nemoclaw-user-manage-sandboxes/SKILL.md` contain matching guidance.

Workflow run details

This is an automated advisory review. A human maintainer must make the final merge decision.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 3

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)
.agents/skills/nemoclaw-user-configure-inference/references/inference-options.md (2)

77-143: ⚠️ Potential issue | 🔴 Critical | 🏗️ Heavy lift

Do not edit autogenerated user skill files directly.

This file is under .agents/skills/nemoclaw-user-*/*.md, which is designated as autogenerated content and should be updated via its generator/source workflow instead of manual edits.

As per coding guidelines, “Autogenerated user skills under .agents/skills/nemoclaw-user-*/*.md must 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 77 - 143, The markdown under the autogenerated user-skill
(containing the routing, models, and tolerance examples and the
NEMOCLAW_PROVIDER hints) was edited directly but must not be changed in-place;
revert this file to the generated state and instead update the generator/source
that outputs this content (the template or generator that emits the routing,
models, tolerance, Host Python requirement, and NEMOCLAW_MODEL_ROUTER_PYTHON
sections), then re-run the generation pipeline so changes appear in the file;
ensure the generator modifies the routing block (routing, checkpoint, tolerance,
encoder) and the models list (name, litellm_model, cost_per_m_input_tokens,
api_base) and commit the regenerated artifact rather than manual edits.

119-121: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Use copyable shell code blocks instead of console with prompts.

These command examples are copyable CLI commands, so they should use a shell language tag (for example, bash) and omit $ prompt markers.

As per coding guidelines, “Copyable CLI code blocks must use language-specific tags such as bash, sh, or powershell, and must not include prompt markers such as $.”

Also applies to: 136-138

🤖 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 119 - 121, Replace the fenced code blocks that currently use the
"console" language and include a leading "$" prompt with copyable shell blocks:
change the language tag from ```console to ```bash (or ```sh) and remove the "$
" prompt marker so the snippet reads like a plain command (e.g.,
NEMOCLAW_PROVIDER=routed NVIDIA_API_KEY=<your-key> nemoclaw onboard
--non-interactive). Apply the same change to the other similar example
containing the NEMOCLAW_PROVIDER ... nemoclaw onboard command referenced in the
file.
🧹 Nitpick comments (1)
docs/about/release-notes.mdx (1)

18-24: ⚡ Quick win

Split each bullet to one sentence per source line.

Several bullets here place multiple sentences on the same line, which breaks the docs source readability rule for sentence-per-line formatting.

As per coding guidelines, "One sentence per line in source (makes diffs readable)."

🤖 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 18 - 24, The release-notes bullets
contain multiple sentences per line which violates the one-sentence-per-line
docs rule; edit each bulleted item so every sentence is on its own source line
(e.g., split the "Public installer..." bullet, the "nemoclaw <name> status..."
bullet, and the other bullets such that each sentence begins on a new line),
preserving existing wording and punctuation and leaving markdown list markers
and links intact; ensure no bullet line contains more than one sentence and run
the docs linter to verify compliance.
🤖 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-manage-policy/references/integration-policy-examples.md:
- Around line 202-213: This change edits an autogenerated user-skill markdown
(the content matching the rule "Autogenerated user skills under
`.agents/skills/nemoclaw-user-*/*.md` must never be edited directly"); revert
the manual edit in that markdown and instead make the update in the source that
generates it (or update the generation pipeline/template) so the file is
regenerated; ensure the change is applied to the generator input (or pipeline
config) that produces integration-policy-examples.md and run the generation job
locally/CI to produce the updated autogenerated file; if needed, add or update a
CI/lint check to reject direct edits to autogenerated
`.agents/skills/nemoclaw-user-*/*.md` files.

In @.agents/skills/nemoclaw-user-overview/references/overview.md:
- Line 8: Replace the unhyphenated compound adjective "on prem" in the sentence
that reads "This enables self-evolving agents to run more safely in clouds, on
prem, RTX PCs, and DGX Spark." with the correctly hyphenated form "on-prem" so
the sentence uses "on-prem" as the compound modifier.

In @.agents/skills/nemoclaw-user-reference/references/commands.md:
- Line 78: Revert any direct edits to the autogenerated
.agents/skills/nemoclaw-user-*/*.md file and instead update the upstream
documentation source/template that generates the onboarding command text (the
source that emits the "Use `--fresh` to ignore any saved onboarding session..."
line for the nemoclaw onboard command), then run the skill
generator/regeneration process to produce a new artifact so the change lands in
the generated commands.md rather than editing the generated file directly.

---

Outside diff comments:
In
@.agents/skills/nemoclaw-user-configure-inference/references/inference-options.md:
- Around line 77-143: The markdown under the autogenerated user-skill
(containing the routing, models, and tolerance examples and the
NEMOCLAW_PROVIDER hints) was edited directly but must not be changed in-place;
revert this file to the generated state and instead update the generator/source
that outputs this content (the template or generator that emits the routing,
models, tolerance, Host Python requirement, and NEMOCLAW_MODEL_ROUTER_PYTHON
sections), then re-run the generation pipeline so changes appear in the file;
ensure the generator modifies the routing block (routing, checkpoint, tolerance,
encoder) and the models list (name, litellm_model, cost_per_m_input_tokens,
api_base) and commit the regenerated artifact rather than manual edits.
- Around line 119-121: Replace the fenced code blocks that currently use the
"console" language and include a leading "$" prompt with copyable shell blocks:
change the language tag from ```console to ```bash (or ```sh) and remove the "$
" prompt marker so the snippet reads like a plain command (e.g.,
NEMOCLAW_PROVIDER=routed NVIDIA_API_KEY=<your-key> nemoclaw onboard
--non-interactive). Apply the same change to the other similar example
containing the NEMOCLAW_PROVIDER ... nemoclaw onboard command referenced in the
file.

---

Nitpick comments:
In `@docs/about/release-notes.mdx`:
- Around line 18-24: The release-notes bullets contain multiple sentences per
line which violates the one-sentence-per-line docs rule; edit each bulleted item
so every sentence is on its own source line (e.g., split the "Public
installer..." bullet, the "nemoclaw <name> status..." bullet, and the other
bullets such that each sentence begins on a new line), preserving existing
wording and punctuation and leaving markdown list markers and links intact;
ensure no bullet line contains more than one sentence and run the docs linter to
verify compliance.
🪄 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: 98c71f94-2a48-4f58-8dea-bd8a0f977b8f

📥 Commits

Reviewing files that changed from the base of the PR and between ca410b5 and ebe47bf.

📒 Files selected for processing (19)
  • .agents/skills/nemoclaw-user-configure-inference/references/inference-options.md
  • .agents/skills/nemoclaw-user-configure-security/references/best-practices.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-manage-sandboxes/evals/evals.json
  • .agents/skills/nemoclaw-user-manage-sandboxes/references/messaging-channels.md
  • .agents/skills/nemoclaw-user-overview/SKILL.md
  • .agents/skills/nemoclaw-user-overview/references/how-it-works.md
  • .agents/skills/nemoclaw-user-overview/references/overview.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.md
  • docs/about/release-notes.mdx
  • docs/manage-sandboxes/messaging-channels.mdx
  • docs/network-policy/integration-policy-examples.mdx
  • docs/reference/commands.mdx
  • docs/security/best-practices.mdx
💤 Files with no reviewable changes (1)
  • .agents/skills/nemoclaw-user-get-started/references/quickstart-hermes.md

Comment thread .agents/skills/nemoclaw-user-overview/references/overview.md Outdated
Comment thread .agents/skills/nemoclaw-user-reference/references/commands.md
@miyoungc miyoungc enabled auto-merge (squash) June 1, 2026 20:49
@miyoungc miyoungc merged commit 23bcf77 into main Jun 1, 2026
31 checks passed
@miyoungc miyoungc deleted the docs/v0.0.56-release-docs branch June 1, 2026 20:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation v0.0.56 Release target

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants