Repository navigation
docs: refresh v0.0.53 notes and skill links #4360
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -4,6 +4,19 @@ | |
|
|
||
| NVIDIA NemoClaw is available in early preview starting March 16, 2026. Use this page to track changes. | ||
|
|
||
| ## v0.0.53 | ||
|
|
||
| NemoClaw v0.0.53 focuses on safer sandbox recreation, stricter onboarding preflight defaults, local inference reliability, policy coverage, and day-two repair workflows: | ||
|
|
||
| - `nemoclaw onboard` backs up workspace state before deleting an existing sandbox during recreation, including sandboxes that are registered but not ready. If the backup is partial or fails, onboarding aborts before delete so workspace, skills, extensions, identity, memory, messaging state, and credentials are not silently dropped. Set `NEMOCLAW_RECREATE_WITHOUT_BACKUP=1` only when you intentionally want a fresh workspace. | ||
| - Under-provisioned container-runtime warnings now default to abort in interactive onboarding. Pressing Enter at the warning stops the run so you can resize Docker Desktop or Colima before the sandbox build stalls. Non-interactive runs continue with a warning, and `NEMOCLAW_IGNORE_RUNTIME_RESOURCES=1` still suppresses the check when you have already accepted the resource trade-off. | ||
| - OpenClaw sandboxes can use the new `openclaw-pricing` policy preset for model-pricing reference fetches from LiteLLM and OpenRouter. NemoClaw suggests this preset during OpenClaw onboarding so session JSONL records can populate `usage.cost` without widening egress beyond the two read-only pricing endpoints. | ||
| - Local Ollama onboarding is more accurate. NemoClaw validates the `/api/tags` response body through the authenticated proxy, honors accepted no-tools overrides through validation and proxy setup, and uses Ollama's reported runtime context length for `contextWindow` unless you set `NEMOCLAW_CONTEXT_WINDOW`. | ||
| - Onboarding and gateway reuse recover from more host-runtime drift. NemoClaw recovers stopped gateways before preserving PVC-backed state, verifies gateway containers before reusing port-conflict state, defers Docker-driver gateway teardown until step `[2/8]`, records Docker-driver sandboxes on macOS, and uses Docker `--gpus` rather than CDI repair on WSL Docker Desktop. | ||
| - The sandbox and integration paths handle more common failures cleanly, including Brave Search credential rewrite through OpenShell providers, Telegram placeholder repair, host-gateway `web_fetch` routing, read-only host targets for `share mount`, live gateway drift in `list`, host-alias Kubernetes invocations, Jetson bridge DNS preflight failures, and non-ready sandboxes during maintenance backups. | ||
| - Hermes startup no longer treats a fresh root-entrypoint layout as locked state, which avoids false locked-layout detection during sandbox boot. | ||
| - Maintainer tooling can export a signed skills catalog, detect untracked files during skills refresh diffs, and run the stale-issue verification workflow added for maintainers. | ||
|
|
||
|
Comment on lines
+7
to
+19
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do not edit autogenerated skill files directly. This file is under the autogenerated skills path and should not be changed in PRs; keep docs edits in As per coding guidelines: "User skills under 🤖 Prompt for AI Agents |
||
| ## v0.0.52 | ||
|
|
||
| NemoClaw v0.0.52 upgrades the bundled OpenClaw runtime, repairs Hermes sandbox startup, restores onboarding ready output, and hardens Slack onboarding, Windows bootstrap, and private-network handling: | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -113,9 +113,8 @@ NemoClaw filters tier suggestions and resume selections by active agent support, | |
| | `custom` | Apply exactly `NEMOCLAW_POLICY_PRESETS`. Previously-applied presets not in the list are removed. Alias: `list`. | | ||
| | `skip` | Skip the policy step entirely. Aliases: `none`, `no`. | | ||
|
|
||
| If you enable Brave Search during onboarding, NemoClaw currently stores the Brave API key in the sandbox's OpenClaw configuration. | ||
| That means the OpenClaw agent can read the key. | ||
| NemoClaw explores an OpenShell-hosted credential path first, but the current OpenClaw Brave runtime does not consume that path end to end yet. | ||
| If you enable Brave Search during onboarding, NemoClaw registers a Brave Search OpenShell provider and keeps `openclaw.json` on an OpenShell credential placeholder. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Fix phrasing for Brave credential placeholder. Line 116 reads awkwardly: “keeps 🤖 Prompt for AI Agents |
||
| At egress, OpenShell rewrites Brave's `X-Subscription-Token` header with the real `BRAVE_API_KEY`. | ||
| Treat Brave Search as an explicit opt-in and use a dedicated low-privilege Brave key. | ||
|
|
||
| For non-interactive onboarding, you must explicitly accept the third-party software notice: | ||
|
|
@@ -178,6 +177,13 @@ In interactive mode, the wizard asks for confirmation before delete and recreate | |
| In non-interactive mode, NemoClaw recreates automatically when the stored selection is readable and differs; if NemoClaw cannot read the stored selection, NemoClaw reuses by default. | ||
| Set `NEMOCLAW_RECREATE_SANDBOX=1` to force recreation even when no drift is detected. | ||
|
|
||
| Before deleting an existing sandbox during recreation, NemoClaw backs up the workspace state (agents, extensions, workspace, skills, hooks, identity, devices, canvas, cron, memory, telegram, wechat, credentials) and restores it into the new sandbox once it is live. | ||
| This applies whether the existing sandbox is ready or marked not-ready, so cross-version upgrades that pass `NEMOCLAW_RECREATE_SANDBOX=1` no longer drop user files under `/sandbox/.openclaw/workspace/`. | ||
| The behaviour matches `nemoclaw <name> rebuild --force`. | ||
| NemoClaw aborts the recreate when the backup cannot complete in full — including when individual state directories or files fail mid-backup — so failed entries are not silently dropped on delete. | ||
| Set `NEMOCLAW_RECREATE_WITHOUT_BACKUP=1` to skip the pre-recreate backup. | ||
| The destination sandbox starts with a fresh workspace. | ||
|
|
||
| Before creating the gateway, the wizard runs preflight checks. | ||
| It verifies that Docker is reachable, warns on untested runtimes such as Podman, and prints host remediation guidance when prerequisites are missing. | ||
| The preflight also enforces the OpenShell version range declared in the blueprint (`min_openshell_version` and `max_openshell_version`). | ||
|
|
@@ -187,6 +193,9 @@ If release metadata is unavailable, the installer uses its bundled fallback pin | |
|
|
||
| When NemoClaw finds an existing gateway to reuse, it probes the host gateway HTTP endpoint before declaring the gateway reusable. | ||
| If the container is running but the upstream is still warming up (for example, immediately after a Docker daemon restart), NemoClaw rebuilds the gateway instead of trusting stale metadata. | ||
| On the Docker-driver gateway path, preflight stays read-only when it detects a stale gateway (for example, a Docker-driver runtime env hash drift). | ||
| It prints a `⚠ Gateway will be recreated when sandbox creation starts` notice and defers the actual teardown to step `[2/8] Starting OpenShell gateway`. | ||
| This means pressing `Ctrl+C` between preflight and step `[2/8]` leaves the running gateway and existing sandbox containers untouched, so `nemoclaw onboard` is safe to run just to check preflight output. | ||
| For Linux Docker-driver gateways, onboarding also checks that a helper container on the OpenShell Docker network can reach `host.openshell.internal:<gateway-port>`. | ||
| If a host firewall blocks that sandbox path, onboarding exits with a `sudo ufw allow from <subnet> to any port <gateway-port> proto tcp` command before it reports the gateway healthy. | ||
| Tune the wait via `NEMOCLAW_REUSE_HEALTH_POLL_COUNT` (default `6`) and `NEMOCLAW_REUSE_HEALTH_POLL_INTERVAL` (default `5` seconds). | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -397,6 +397,9 @@ Default Colima ships with 2 vCPU and 2 GiB of memory, which is not enough headro | |
| On macOS Apple Silicon, the build can stall part-way through with no progress and no error, leaving the wizard waiting indefinitely. | ||
|
|
||
| Preflight inspects `docker info` for `NCPU` and `MemTotal` and prints a warning when the runtime falls below 4 vCPU or 8 GiB. | ||
| In interactive onboarding, the warning prompt defaults to abort, so pressing Enter stops the run before the sandbox build reaches the likely stall point. | ||
| Type `y` only when you intentionally want to continue on the smaller runtime. | ||
| Non-interactive onboarding prints the warning and continues. | ||
| On Colima, raise the resources before re-running onboard: | ||
|
Comment on lines
+400
to
403
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Generated skill content should come from source docs, not direct edits. These updates are in an autogenerated skill file and should be produced by the docs-to-skills pipeline from As per coding guidelines: "User skills under Also applies to: 780-795, 1190-1194, 1211-1215 🤖 Prompt for AI Agents |
||
|
|
||
| ```console | ||
|
|
@@ -774,6 +777,23 @@ WhatsApp pairs entirely inside the sandbox. | |
| NemoClaw advertises WhatsApp for OpenClaw and Hermes sandboxes after you add the channel on the host. | ||
| Run `openclaw channels login --channel whatsapp` inside OpenClaw sandboxes, or run `hermes whatsapp` inside Hermes sandboxes. | ||
|
|
||
| ### `scripts/rcf_patch.py` is missing from the blueprint | ||
|
|
||
| `scripts/rcf_patch.py` is intentionally absent from current NemoClaw blueprints. | ||
| Older QA plans used that helper for a Dockerfile "Patch-4" test that corrupted the build-time `replaceConfigFile` monkey-patch and expected `ERROR: Patch 4 (replaceConfigFile EACCES) not applied`. | ||
| The old Patch-4 fail-closed test no longer applies because NemoClaw no longer patches OpenClaw's compiled `replaceConfigFile` source at image build time. | ||
|
|
||
| Current sandboxes use a mutable-default config model instead. | ||
| Before a reviewed host-side lockdown, `/sandbox/.openclaw/openclaw.json` is group-writable by the sandbox and gateway users, so OpenClaw config mutations should write normally rather than requiring an EACCES swallow. | ||
| After lockdown, runtime config mutations should fail cleanly or route users to the supported host-side NemoClaw command. | ||
|
|
||
| To validate this area now, use the config lifecycle tests instead of looking for `rcf_patch.py`: | ||
|
|
||
| ```console | ||
| $ npm run build:cli | ||
| $ npm test -- test/repro-2681-group-writable.test.ts | ||
| ``` | ||
|
|
||
| ### `openclaw config set` or `unset` is blocked inside the sandbox | ||
|
|
||
| This is expected. | ||
|
|
@@ -1167,7 +1187,10 @@ Recent NVIDIA Container Toolkit installs configure the Docker daemon for Contain | |
| If no `nvidia.com/gpu` CDI spec has been generated on the host yet, gateway start fails with `Docker responded with status code 500: CDI device injection failed: unresolvable CDI devices nvidia.com/gpu=all`. | ||
| The standard NemoClaw installer detects this gap before onboarding, first tries to enable the NVIDIA CDI refresh systemd units, and falls back to generating the spec directly with `nvidia-ctk`. | ||
| If you run `nemoclaw onboard` directly, preflight prints the manual remediation instead. | ||
| The underlying fix is the same on any Docker host whose `docker info` advertises a non-empty `CDISpecDirs`. | ||
| The native Linux fix is the same on Docker hosts whose `docker info` advertises a non-empty `CDISpecDirs`. | ||
| On WSL with Docker Desktop, Docker may advertise CDI directories even though `--device nvidia.com/gpu=all` is not usable from the WSL distro. | ||
| For that runtime, NemoClaw skips Linux CDI repair and uses Docker's `--gpus` compatibility path for sandbox GPU access. | ||
| This compatibility path can be retired once Docker Desktop exposes usable `nvidia.com/gpu` CDI specs inside WSL, or once OpenShell no longer requires host-visible CDI specs for Docker Desktop WSL GPU passthrough. | ||
|
|
||
| Enable the refresh units, verify they list `nvidia.com/gpu` entries, then rerun onboarding: | ||
|
|
||
|
|
@@ -1185,6 +1208,12 @@ $ sudo nvidia-ctk cdi generate --output=/etc/cdi/nvidia.yaml | |
| $ nvidia-ctk cdi list | ||
| ``` | ||
|
|
||
| On WSL with Docker Desktop, confirm Docker Desktop WSL integration is enabled for your distro and verify Docker GPU access from WSL: | ||
|
|
||
| ```console | ||
| $ docker run --rm --gpus all nvcr.io/nvidia/k8s/cuda-sample:nbody nbody -gpu -benchmark | ||
| ``` | ||
|
|
||
| If GPU passthrough is not required on this host, rerun onboarding with `--no-gpu` instead. | ||
|
|
||
| ### Docker GPU patch failed during sandbox create | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do not edit autogenerated skill files directly.
This change is in an autogenerated skill file and should be produced by the docs-to-skills pipeline, not hand-edited in place.
As per coding guidelines: "User skills under
.agents/skills/nemoclaw-user-*/*.mdare autogenerated and must never be edited directly"🤖 Prompt for AI Agents