Skip to content

fix(installer): default public installs to lkg#4613

Merged
cv merged 2 commits into
mainfrom
codex/install-default-lkg
Jun 1, 2026
Merged

fix(installer): default public installs to lkg#4613
cv merged 2 commits into
mainfrom
codex/install-default-lkg

Conversation

@cv
Copy link
Copy Markdown
Collaborator

@cv cv commented Jun 1, 2026

Summary

Switches the public installer default from the mutable latest tag to the lkg tag so curl-piped installs and update checks follow the last-known-good release pointer by default. Keeps explicit NEMOCLAW_INSTALL_REF and NEMOCLAW_INSTALL_TAG overrides working as before.

Related Issue

None.

Changes

  • Default the root bootstrap installer and versioned scripts/install.sh payload to lkg when no install ref/tag override is set.
  • Treat lkg as a mutable install ref for installer version display, matching the existing latest handling.
  • Update nemoclaw update --check version discovery to resolve the maintained lkg tag instead of latest.
  • Update installer/internal tests and the command reference docs for the new default.

Type of Change

  • Code change (feature, bug fix, or refactor)
  • Code change with doc updates
  • Doc only (prose changes, no code sample modifications)
  • Doc only (includes code sample changes)

Verification

  • npx prek run --all-files passes
  • npm test passes
  • Tests added or updated for new or changed behavior
  • No secrets, API keys, or credentials committed
  • Docs updated for user-facing behavior changes
  • npm run docs builds without warnings (doc changes only)
  • Doc pages follow the style guide (doc changes only)
  • New doc pages include SPDX header and frontmatter (new pages only)

Additional verification performed:

  • npx vitest run test/install-preflight.test.ts test/internal-cli.test.ts src/lib/domain/installer/ref.test.ts src/lib/actions/installer/plan.test.ts src/lib/actions/update.test.ts passed.
  • npm run build:cli passed.
  • cd nemoclaw && npm run build passed.
  • npm run checks passed.
  • npm exec -- tsx scripts/check-env-var-docs.ts passed.
  • python3 scripts/docs-to-skills.py docs/ .agents/skills/ --prefix nemoclaw-user --doc-platform fern-mdx --dry-run passed.
  • npm run docs passed with 2 pre-existing Fern warnings.
  • npx prek run --all-files and ./node_modules/.bin/prek run --all-files were blocked before hook execution by certificate/repo-fetch errors (self-signed certificate in certificate chain; GitHub 503 while fetching scop/pre-commit-shfmt).
  • Full npm test was run after rebuilding generated artifacts and failed in unrelated sandbox/rebuild/status tests: 12 failed files, 44 failed tests, 6242 passed, 25 skipped.

Signed-off-by: Carlos Villela cvillela@nvidia.com

Summary by CodeRabbit

  • Improvements

    • Default installation reference changed from "latest" to "lkg"; installer and update flows now follow the maintained "lkg" tag by default.
  • Documentation

    • Environment variable help and docs updated to show lkg as the default install tag; guidance updated to explain maintained-tag behavior.
  • Tests

    • Test expectations and CLI help tests updated to reflect the new lkg default.

Signed-off-by: Carlos Villela <cvillela@nvidia.com>
@cv cv added the documentation Improvements or additions to documentation label Jun 1, 2026
@cv cv self-assigned this Jun 1, 2026
@copy-pr-bot
Copy link
Copy Markdown

copy-pr-bot Bot commented Jun 1, 2026

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@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: 53d05bdd-6a0d-4ad8-a0ba-1c2930f1111f

📥 Commits

Reviewing files that changed from the base of the PR and between 4a10853 and e6d687d.

📒 Files selected for processing (4)
  • .agents/skills/nemoclaw-maintainer-cut-release-tag/SKILL.md
  • docs/manage-sandboxes/lifecycle.mdx
  • docs/reference/commands.mdx
  • scripts/bump-version.ts
✅ Files skipped from review due to trivial changes (2)
  • scripts/bump-version.ts
  • docs/reference/commands.mdx

📝 Walkthrough

Walkthrough

Defaults for the NemoClaw installer ref/tag change from "latest" to the maintained "lkg": shell and TypeScript resolution now use DEFAULT_INSTALL_REF="lkg", mutable-ref handling is broadened, maintained-version git lookups query lkg refs, and tests/docs updated to match.

Changes

Maintained install tag defaults and infrastructure

Layer / File(s) Summary
Shell script maintained defaults
install.sh, scripts/install.sh
Introduces DEFAULT_INSTALL_REF="lkg", is_mutable_install_ref() and updates resolve_release_tag()/resolve_installer_version() to treat latest, lkg, and refs/tags/* as mutable. CLI help/usage now shows default: lkg.
TypeScript installer ref resolution
src/lib/domain/installer/ref.ts, src/lib/domain/installer/ref.test.ts
Adds DEFAULT_INSTALL_REF and MUTABLE_INSTALL_REFS. resolveInstallRef() now defaults to lkg when no env is set; installerVersionFromRef() treats lkg and refs/tags/lkg as mutable (returns null). Tests updated to use the constant.

Maintained version resolution from git

Layer / File(s) Summary
Maintained tag version lookup
src/lib/actions/update.ts, src/lib/actions/update.test.ts
Adds NEMOCLAW_MAINTAINED_INSTALL_TAG = "lkg" and replaces the previous latest-tag resolution with getMaintainedNemoClawVersionFromGitTag(), querying refs/tags/lkg and refs/tags/lkg^{} and mapping tag SHAs to v* versions. runUpdateAction() default wiring updated; tests adapted to stub git responses.

Test updates and documentation

Layer / File(s) Summary
Integration tests and reference docs
src/lib/actions/installer/plan.test.ts, test/install-preflight.test.ts, test/internal-cli.test.ts, .agents/skills/*, docs/reference/commands.mdx, docs/manage-sandboxes/lifecycle.mdx, scripts/bump-version.ts
Update test expectations to expect installRef: "lkg" by default; update --help output assertions to default: lkg; add docs and release-skill notes stating lkg is the maintained installer tag promoted manually by admins and may lag latest during validation.

🎯 3 (Moderate) | ⏱️ ~20 minutes

Suggested labels: fix

"I hopped from latest to lkg with care,
The installer now follows the tag admins bear.
Scripts, tests, and docs all sing in tune,
A steadier path beneath the moon.
🐰✨"

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 14.29% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and specifically describes the main change: switching the default installer behavior from 'latest' to 'lkg' across the codebase.
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 docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch codex/install-default-lkg

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

PR Review Advisor

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

Workflow run details

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

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 1, 2026

E2E Advisor Recommendation

Required E2E: cloud-onboard-e2e, cloud-e2e
Optional E2E: upgrade-stale-sandbox-e2e, macos-e2e

Dispatch hint: cloud-onboard-e2e,cloud-e2e

Auto-dispatched E2E: cloud-onboard-e2e, cloud-e2e via nightly-e2e.yaml at e6d687d9ff0749ba9bba705912a0e8af926bd38enightly run

Workflow run

Full advisor summary

E2E Recommendation Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required E2E

  • cloud-onboard-e2e (high; live Docker/OpenShell sandbox plus NVIDIA_API_KEY cloud onboarding): Most targeted existing coverage for the public installer path: it runs the curl-style installer, clones the selected ref, performs non-interactive cloud onboarding, then verifies sandbox health and security checks. Required because the PR changes public installer ref selection and installer payload behavior.
  • cloud-e2e (high; full install/onboard/live inference flow with NVIDIA_API_KEY): Validates the complete source-checkout install.sh path from this PR through onboarding, sandbox readiness, CLI operations, and live inference. Required because scripts/install.sh changes can affect the normal repo/source installer path independently from the public bootstrap path.

Optional E2E

  • upgrade-stale-sandbox-e2e (high; builds an old sandbox image and performs rebuild lifecycle validation): Useful adjacent confidence for update/upgrade lifecycle docs and installer-installed CLI behavior: it installs current NemoClaw, detects a stale sandbox, rebuilds it, and verifies upgrade-sandboxes reports clean. It does not directly exercise nemoclaw update or lkg tag resolution, so it is optional rather than merge-blocking.
  • macos-e2e (medium-high; macOS build plus full E2E when Docker is available): Optional cross-platform installer confidence because shell installer changes can regress macOS PATH/install behavior. This PR primarily changes Linux/public release-ref semantics, so macOS is useful but not required.

New E2E recommendations

  • public installer default lkg selection (high): Existing cloud-onboard-e2e overrides NEMOCLAW_INSTALL_REF/NEMOCLAW_INSTALL_TAG to the PR head so it validates the public bootstrap mechanics but not the new no-override default that should fetch lkg instead of latest.
    • Suggested test: Add a public-installer-default-ref E2E or hermetic script-runner job that runs the bootstrap with no NEMOCLAW_INSTALL_REF/TAG against a controlled git remote and asserts the fetched ref is lkg, not latest, before any onboarding side effects.
  • nemoclaw update maintained-tag flow (high): The changed update action resolves the maintained version from refs/tags/lkg and then runs the maintained installer with sanitized env, but existing E2E coverage focuses on install/onboard and upgrade-sandboxes rather than the actual nemoclaw update --check / nemoclaw update --yes user flow.
    • Suggested test: Add an update-maintained-tag E2E that installs an older package/managed clone, stubs or controls remote tags so lkg points at a newer semver, verifies nemoclaw update --check reports the maintained version, and verifies nemoclaw update --yes invokes the installer without inherited NEMOCLAW_INSTALL_REF/TAG.

Dispatch hint

  • Workflow: E2E / Nightly
  • jobs input: cloud-onboard-e2e,cloud-e2e

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 1, 2026

E2E Scenario Advisor Recommendation

Required scenario E2E: ubuntu-repo-cloud-openclaw
Optional scenario E2E: ubuntu-repo-cloud-hermes, macos-repo-cloud-openclaw, wsl-repo-cloud-openclaw

Dispatch required scenario E2E:

  • gh workflow run e2e-scenarios.yaml --ref <pr-head-ref> --field scenarios=ubuntu-repo-cloud-openclaw

Workflow run

Full scenario advisor summary

E2E Scenario Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required scenario E2E

  • ubuntu-repo-cloud-openclaw: Installer/default install-ref and maintained update-path code changed. The Ubuntu repo OpenClaw scenario is the primary scenario path that exercises repo checkout installation, CLI availability, OpenShell setup, onboarding preflight, and baseline smoke behavior on the standard runner.
    • Dispatch: gh workflow run e2e-scenarios.yaml --ref <pr-head-ref> --field scenarios=ubuntu-repo-cloud-openclaw

Optional scenario E2E

  • ubuntu-repo-cloud-hermes: Optional adjacent coverage for the same repo installer/onboarding surface under the Hermes agent profile, relevant because update/install guidance preserves Hermes agent selection but OpenClaw is the primary required path.
    • Dispatch: gh workflow run e2e-scenarios.yaml --ref <pr-head-ref> --field scenarios=ubuntu-repo-cloud-hermes
  • macos-repo-cloud-openclaw: Optional platform coverage for shell installer/CLI availability behavior on macOS. Special-runner/platform scenarios should remain optional unless they are the only path for the change.
    • Dispatch: gh workflow run e2e-scenarios.yaml --ref <pr-head-ref> --field scenarios=macos-repo-cloud-openclaw
  • wsl-repo-cloud-openclaw: Optional platform coverage for shell installer/CLI availability behavior under WSL. The standard Ubuntu scenario is the primary target; WSL is adjacent platform validation.
    • Dispatch: gh workflow run e2e-scenarios.yaml --ref <pr-head-ref> --field scenarios=wsl-repo-cloud-openclaw

Relevant changed files

  • install.sh
  • scripts/install.sh
  • src/lib/actions/update.ts
  • src/lib/domain/installer/ref.ts

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.

🧹 Nitpick comments (2)
docs/reference/commands.mdx (1)

1382-1382: ⚡ Quick win

Replace the clause colon with comma/period punctuation.

Line 1382 uses a colon as general punctuation in prose (For internal installer commands: ...). Please rewrite with a comma or split sentence.

As per coding guidelines, "Colons should only introduce a list. Flag colons used as general punctuation between clauses."

🤖 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 1382, The table row for the environment
variable NEMOCLAW_INSTALL_TAG uses a colon as general punctuation ("For internal
installer commands: the release tag to install."); update the sentence to remove
the colon and either use a comma or split into two sentences (e.g., "For
internal installer commands, the release tag to install." or "For internal
installer commands. The release tag to install."). Edit the text associated with
NEMOCLAW_INSTALL_TAG in the table so it conforms to the guideline that colons
only introduce lists.
src/lib/domain/installer/ref.test.ts (1)

17-33: ⚡ Quick win

Add one assertion for refs/tags/lkg mutable-ref behavior.

The new mutable-ref set includes refs/tags/lkg, but the updated test only asserts lkg. A single extra case would guard this new branch.

Proposed test addition
     expect(
       resolveInstallerVersion({
         defaultVersion: "0.1.0",
         env: { NEMOCLAW_INSTALL_TAG: "lkg" },
         gitDescribeVersion: "v2.0.0-4-gabc",
         packageJsonVersion: "3.0.0",
         stampedVersion: "2.0.0",
       }),
     ).toBe("2.0.0-4-gabc");
+    expect(
+      resolveInstallerVersion({
+        defaultVersion: "0.1.0",
+        env: { NEMOCLAW_INSTALL_TAG: "refs/tags/lkg" },
+        gitDescribeVersion: "v2.0.0-4-gabc",
+        packageJsonVersion: "3.0.0",
+        stampedVersion: "2.0.0",
+      }),
+    ).toBe("2.0.0-4-gabc");
🤖 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 `@src/lib/domain/installer/ref.test.ts` around lines 17 - 33, Add one more
assertion in the test for resolveInstallerVersion to cover the new mutable-ref
form "refs/tags/lkg": replicate the existing case that asserts behavior for env
NEMOCLAW_INSTALL_TAG: "lkg" but pass the tag as "refs/tags/lkg" (keeping other
inputs same) and assert the same resulting version ("2.0.0-4-gabc"); update the
test block in src/lib/domain/installer/ref.test.ts near the other expectations
so the new branch for refs/tags/... is exercised.
🤖 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.

Nitpick comments:
In `@docs/reference/commands.mdx`:
- Line 1382: The table row for the environment variable NEMOCLAW_INSTALL_TAG
uses a colon as general punctuation ("For internal installer commands: the
release tag to install."); update the sentence to remove the colon and either
use a comma or split into two sentences (e.g., "For internal installer commands,
the release tag to install." or "For internal installer commands. The release
tag to install."). Edit the text associated with NEMOCLAW_INSTALL_TAG in the
table so it conforms to the guideline that colons only introduce lists.

In `@src/lib/domain/installer/ref.test.ts`:
- Around line 17-33: Add one more assertion in the test for
resolveInstallerVersion to cover the new mutable-ref form "refs/tags/lkg":
replicate the existing case that asserts behavior for env NEMOCLAW_INSTALL_TAG:
"lkg" but pass the tag as "refs/tags/lkg" (keeping other inputs same) and assert
the same resulting version ("2.0.0-4-gabc"); update the test block in
src/lib/domain/installer/ref.test.ts near the other expectations so the new
branch for refs/tags/... is exercised.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 18aeb730-2bd0-4c6d-9d3a-33dec8a3d527

📥 Commits

Reviewing files that changed from the base of the PR and between 9248f5e and 4a10853.

📒 Files selected for processing (10)
  • docs/reference/commands.mdx
  • install.sh
  • scripts/install.sh
  • src/lib/actions/installer/plan.test.ts
  • src/lib/actions/update.test.ts
  • src/lib/actions/update.ts
  • src/lib/domain/installer/ref.test.ts
  • src/lib/domain/installer/ref.ts
  • test/install-preflight.test.ts
  • test/internal-cli.test.ts

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 1, 2026

Selective E2E Results — ✅ All requested jobs passed

Run: 26770522465
Target ref: 4a10853826c2a0480d609e1b2f2a7bf895bd3163
Workflow ref: main
Requested jobs: cloud-onboard-e2e,cloud-e2e
Summary: 2 passed, 0 failed, 0 skipped

Job Result
cloud-e2e ✅ success
cloud-onboard-e2e ✅ success

Signed-off-by: Carlos Villela <cvillela@nvidia.com>
@cv
Copy link
Copy Markdown
Collaborator Author

cv commented Jun 1, 2026

Addressed the release-tag note in e6d687d: lkg remains a manually admin-promoted known-good tag and is not moved by automated release tooling. The release skill, update docs, and installer env-var docs now call out that lkg may intentionally lag latest while validation completes.

Copy link
Copy Markdown
Contributor

@ericksoa ericksoa left a comment

Choose a reason for hiding this comment

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

Approved for auto-merge at head e6d687d.

@ericksoa ericksoa enabled auto-merge (squash) June 1, 2026 17:43
@cv cv disabled auto-merge June 1, 2026 17:45
@cv cv merged commit 0578c72 into main Jun 1, 2026
24 checks passed
@cv cv deleted the codex/install-default-lkg branch June 1, 2026 17:45
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 1, 2026

Selective E2E Results — ✅ All requested jobs passed

Run: 26771498324
Target ref: e6d687d9ff0749ba9bba705912a0e8af926bd38e
Workflow ref: main
Requested jobs: cloud-onboard-e2e,cloud-e2e
Summary: 2 passed, 0 failed, 0 skipped

Job Result
cloud-e2e ✅ success
cloud-onboard-e2e ✅ success

miyoungc added a commit that referenced this pull request 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

- #4613 -> `docs/manage-sandboxes/lifecycle.mdx`,
`docs/reference/commands.mdx`, `docs/about/release-notes.mdx`: Documents
that public installs and `nemoclaw update` follow the maintained `lkg`
tag by default.
- #4419 -> `docs/about/release-notes.mdx`: Notes that non-interactive
Linux installs can reactivate Docker group membership and continue in
one installer run when `sg docker` is available.
- #4550 -> `docs/reference/commands.mdx`,
`docs/about/release-notes.mdx`: Captures live sandbox agent-version
probing for status, connect, and upgrade checks.
- #4609 -> `docs/inference/use-local-inference.mdx`,
`docs/about/release-notes.mdx`: Captures the GPU Docker-driver
host-network local-inference reachability gate.
- #4607 -> `docs/manage-sandboxes/messaging-channels.mdx`,
`docs/reference/commands.mdx`, `docs/about/release-notes.mdx`: Documents
compact WhatsApp QR pairing guidance and gateway/session diagnostics.
- #4582 -> `docs/manage-sandboxes/messaging-channels.mdx`,
`docs/reference/commands.mdx`, `docs/about/release-notes.mdx`: Reflects
Slack credential validation before enabling the channel.
- #4554 -> `docs/manage-sandboxes/messaging-channels.mdx`,
`docs/reference/troubleshooting.mdx`, `docs/about/release-notes.mdx`:
Keeps Telegram allowlist alias guidance in the generated user skills and
release notes.
- #4563 -> `docs/reference/commands.mdx`,
`docs/about/release-notes.mdx`: Includes the new `nemoclaw <name> skill
remove <skill>` command in command docs and release notes.
- #4566 -> `docs/reference/commands.mdx`,
`docs/about/release-notes.mdx`: Documents the `nemoclaw inference set`
redirect boundary when `--provider` or `--model` is missing.
- #4323 -> `docs/reference/commands.mdx`,
`docs/about/release-notes.mdx`: Captures per-sandbox status JSON
support.
- #4506 -> `docs/reference/commands.mdx`,
`docs/about/release-notes.mdx`: Captures debug command sandbox-name
validation and safer tarball writing.
- #4569 -> `docs/network-policy/integration-policy-examples.mdx`,
`docs/about/release-notes.mdx`: Documents that the `pypi` preset allows
`/usr/local/bin/uv`.
- #4579 -> `docs/network-policy/integration-policy-examples.mdx`,
`docs/about/release-notes.mdx`: Captures observable Jira preset
validation guidance.
- #4229 -> `docs/manage-sandboxes/lifecycle.mdx`,
`docs/reference/commands.mdx`, `docs/about/release-notes.mdx`: Documents
user-data preservation defaults for uninstall.
- #4399 -> `docs/reference/commands.mdx`,
`docs/about/release-notes.mdx`: Captures CPU-only sandbox intent
preservation across rebuilds.
- #4058 -> `docs/reference/commands.mdx`,
`docs/about/release-notes.mdx`: Captures safer snapshot restore behavior
around existing destinations.
- #4155 and #4460 -> skipped by `docs/.docs-skip`: Removed skipped
experimental command terms from source docs and generated skill evals
instead of documenting those features.

## 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)`.

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Documentation**
* Expanded Model Router setup with YAML examples, flow diagrams, and
credential handling; strengthened agent-config immutability and
integrity guidance; messaging channels updated (Telegram aliases,
WhatsApp pairing/diagnostics); CLI docs revised (GPU detection,
inference set behavior, uninstall/rebuild preservation); overview
rebranded to NemoClaw and added v0.0.56 release notes.

* **New Features**
* Added `nemoclaw <name> channels status` (messaging diagnostics, JSON);
added `nemoclaw <name> skill remove`; Hermes no longer marked
experimental; DGX Spark quickstart sandbox-name note.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants