diff --git a/.agents/skills/nemoclaw-user-configure-inference/SKILL.md b/.agents/skills/nemoclaw-user-configure-inference/SKILL.md index 5bb7228151..376f08b57c 100644 --- a/.agents/skills/nemoclaw-user-configure-inference/SKILL.md +++ b/.agents/skills/nemoclaw-user-configure-inference/SKILL.md @@ -171,6 +171,8 @@ If your server does not require authentication, enter any non-empty string (for NemoClaw validates the endpoint by sending a test inference request before continuing. The wizard probes `/v1/chat/completions` by default for the compatible-endpoint provider. If you set `NEMOCLAW_PREFERRED_API=openai-responses`, NemoClaw probes `/v1/responses` instead and only selects it when the response includes the streaming events OpenClaw requires. +If a reasoning model returns only reasoning content before producing a final answer, NemoClaw retries the smoke request with a larger response budget. +Route, configuration, and authentication failures still fail immediately. ### Non-Interactive Setup @@ -343,6 +345,8 @@ $ nemoclaw status ``` The output shows the provider label (for example, "Local vLLM" or "Other OpenAI-compatible endpoint") and the active model. +For Local Ollama, status also checks the authenticated proxy when a proxy token is available. +If `Inference` is healthy but `Inference (auth proxy)` is not, rerun onboarding to repair the proxy path that sandbox requests use. ## Step 8: Switch Models at Runtime diff --git a/.agents/skills/nemoclaw-user-get-started/SKILL.md b/.agents/skills/nemoclaw-user-get-started/SKILL.md index f38521618f..1fd8ea4578 100644 --- a/.agents/skills/nemoclaw-user-get-started/SKILL.md +++ b/.agents/skills/nemoclaw-user-get-started/SKILL.md @@ -36,6 +36,7 @@ If `nemoclaw` is not found after install, run `source ~/.bashrc` (or `source ~/. On Linux, the installer checks Docker before it installs NemoClaw. If Docker is missing, the installer downloads the official Docker convenience script, asks for `sudo`, installs Docker, and starts the Docker service when systemd is available. If Docker is installed but your current shell cannot use the Docker socket yet, the installer adds your user to the `docker` group when needed and exits with a recovery command. +On macOS, the installer uses the Docker-driver OpenShell gateway path with Docker Desktop or Colima. ```console $ newgrp docker @@ -312,6 +313,7 @@ You can chat with the agent from the terminal or the browser. The onboard wizard starts a background port forward to the sandbox dashboard, then prints the dashboard URL in the install summary. The default host port is `18789`. If that port is already taken, NemoClaw uses the next free dashboard port, such as `18790`, and prints that port in the final URL. +If the chosen port becomes occupied after the sandbox build starts, onboarding rolls back the newly-created sandbox and asks you to retry instead of printing an unreachable dashboard URL. The gateway token is redacted from displayed output; retrieve it explicitly when the browser asks for authentication. ```text diff --git a/.agents/skills/nemoclaw-user-get-started/references/prerequisites.md b/.agents/skills/nemoclaw-user-get-started/references/prerequisites.md index 30e2f3d7a7..3c4c4207a0 100644 --- a/.agents/skills/nemoclaw-user-get-started/references/prerequisites.md +++ b/.agents/skills/nemoclaw-user-get-started/references/prerequisites.md @@ -27,6 +27,8 @@ On Linux, the installer can install Docker, start the Docker service, and add yo If the group change is not active in the current shell, the installer exits with `newgrp docker` guidance before it starts onboarding. If you choose the native Linux Ollama install path, the onboard wizard also requires `zstd` for Ollama archive extraction. On Debian and Ubuntu, NemoClaw installs `zstd` with `apt-get` if it is missing; on other Linux distributions, install `zstd` before onboarding. +On macOS, NemoClaw uses the Docker-driver OpenShell gateway path with Docker Desktop or Colima. +You do not need to install or sign a separate OpenShell VM driver helper for standard macOS onboarding. :::{warning} OpenShell Lifecycle For NemoClaw-managed environments, use `nemoclaw onboard` when you need to create or recreate the OpenShell gateway or sandbox. diff --git a/.agents/skills/nemoclaw-user-manage-sandboxes/references/messaging-channels.md b/.agents/skills/nemoclaw-user-manage-sandboxes/references/messaging-channels.md index f759980a55..a9c8c6c9fc 100644 --- a/.agents/skills/nemoclaw-user-manage-sandboxes/references/messaging-channels.md +++ b/.agents/skills/nemoclaw-user-manage-sandboxes/references/messaging-channels.md @@ -86,6 +86,8 @@ $ nemoclaw my-assistant channels add slack ``` `channels add` prompts for missing credentials, registers the bridge with the OpenShell gateway, updates the sandbox registry, and asks whether to rebuild immediately. +The command accepts mixed-case input such as `Telegram`, then stores and prints the canonical lowercase channel name. +If the matching built-in network policy preset exists but is not applied yet, the command prints a `policy-add ` hint after it registers the channel. Choose the rebuild so the running sandbox image picks up the new channel. If you need optional channel settings such as `TELEGRAM_ALLOWED_IDS`, `TELEGRAM_REQUIRE_MENTION`, `DISCORD_SERVER_ID`, `DISCORD_USER_ID`, or `DISCORD_REQUIRE_MENTION`, export them before the rebuild starts. If you defer the rebuild, apply the change later: diff --git a/.agents/skills/nemoclaw-user-overview/references/release-notes.md b/.agents/skills/nemoclaw-user-overview/references/release-notes.md index 39a381ecfd..2d1f7fe5f5 100644 --- a/.agents/skills/nemoclaw-user-overview/references/release-notes.md +++ b/.agents/skills/nemoclaw-user-overview/references/release-notes.md @@ -4,6 +4,20 @@ NVIDIA NemoClaw is available in early preview starting March 16, 2026. Use this page to track changes. +## v0.0.42 + +NemoClaw v0.0.42 improves onboarding, status diagnostics, local inference checks, and messaging setup: + +- `nemoclaw onboard` uses the Docker-driver OpenShell gateway path on macOS and no longer requires VM driver helper assets for standard macOS onboarding. +- Dashboard port selection probes occupied ports more thoroughly, including root-owned listeners on macOS, and rolls back a newly-created sandbox if the dashboard forward cannot start after the image build. +- `nemoclaw status` shows `Inference` and `Connected` fields for each listed sandbox, and cloudflared service output now distinguishes stopped, invalid PID file, and stale PID states with a `nemoclaw tunnel start` recovery hint. +- Local Ollama status and doctor checks now probe the authenticated proxy in addition to the backend, so a broken proxy is reported separately from a healthy `127.0.0.1:11434` backend. +- Compatible OpenAI endpoint validation retries reasoning-only smoke responses with a larger output budget before classifying the setup as a model output budget problem instead of a route failure. +- `channels add` and `channels remove` normalize channel names before saving or rebuilding, and `channels add` hints when a matching built-in policy preset exists but is not applied yet. +- GPU recovery and uninstall output now use registry-aware recovery commands and clearer gateway removal wording. +- Onboarding applies selected built-in policy presets in a single policy update when possible, while preserving the final live policy and registry state. +- The installer handles unchanged user-local CLI shims idempotently, avoiding duplicate shim-creation messages during install-plus-verify flows. + ## v0.0.41 NemoClaw v0.0.41 improves Docker-driver onboarding and release compatibility: diff --git a/.agents/skills/nemoclaw-user-reference/references/commands.md b/.agents/skills/nemoclaw-user-reference/references/commands.md index a5700191f4..2e7769355f 100644 --- a/.agents/skills/nemoclaw-user-reference/references/commands.md +++ b/.agents/skills/nemoclaw-user-reference/references/commands.md @@ -336,6 +336,8 @@ The command probes every inference provider and reports one of three states on t Local providers (Ollama, vLLM) probe the host-side health endpoint. Remote providers (NVIDIA Endpoints, OpenAI, Anthropic, Gemini) use a lightweight reachability check; any HTTP response, including `401` or `403`, counts as reachable. No API keys are sent. +For Local Ollama, the command also probes the authenticated proxy and prints an `Inference (auth proxy)` line when a proxy token is available. +Use that line to distinguish a healthy backend from a broken proxy path that the sandbox uses for inference. For cloud-only providers, the output omits the NIM status line unless a NIM container is registered or an unexpected NIM container is running. If the sandbox or gateway cannot be verified, the command exits non-zero instead of reporting healthy inference from stale registry state. Gateway and dashboard health checks treat HTTP `401` from device auth as a live service, not as an offline gateway. @@ -568,6 +570,8 @@ $ nemoclaw my-assistant channels list Store credentials for a messaging channel (`telegram`, `discord`, or `slack`) and rebuild the sandbox so the image picks up the new channel. The command prompts for any missing token, registers it with the OpenShell gateway, then asks whether to rebuild immediately. Running `add` for an already-configured channel simply overwrites the stored tokens — the operation is idempotent. +Channel names are trimmed and lowercased before NemoClaw stores credentials, names bridge providers, or prints rebuild messages. +After a successful add, NemoClaw prints a `policy-add ` hint when a matching built-in network policy preset exists but is not applied to the sandbox yet. ```console $ nemoclaw my-assistant channels add telegram @@ -882,6 +886,7 @@ This command remains as a compatibility alias to `nemoclaw tunnel stop`. Show the sandbox list and the status of host auxiliary services (for example cloudflared). Pass `--json` for machine-readable output with registered sandboxes, service state, inference routes, and messaging health. +For each listed sandbox, the text output includes the configured inference provider and model plus whether an active SSH session is connected. ```console $ nemoclaw status @@ -893,6 +898,7 @@ The command suggests `openshell gateway start --name nemoclaw` or `nemoclaw onbo It exits with code `1` so shell scripts and CI can detect the degraded state from `$?`. For `--json`, the structured output includes `gatewayHealth`, and the exit code is set after the report is generated. A clean machine with no registered sandboxes keeps the legacy `0` exit because no gateway is expected to be configured yet. +If cloudflared is installed but not running, the host-service section reports whether the PID file is missing, invalid, or points at a dead process, then suggests `nemoclaw tunnel start` as the recovery command. ### `nemoclaw inference get` diff --git a/.agents/skills/nemoclaw-user-reference/references/troubleshooting.md b/.agents/skills/nemoclaw-user-reference/references/troubleshooting.md index d49c89c6f7..f7c8487d2a 100644 --- a/.agents/skills/nemoclaw-user-reference/references/troubleshooting.md +++ b/.agents/skills/nemoclaw-user-reference/references/troubleshooting.md @@ -147,6 +147,8 @@ When the lookup returns an answer, retry onboarding. The NemoClaw dashboard uses port `18789` by default and the gateway uses port `8080`. If another sandbox already owns the dashboard port, onboarding scans ports `18789` through `18799` and uses the next free port. If all ports in that range are occupied, the error lists the owner for each port and suggests using `--control-ui-port` with a port outside the range. +On macOS, the port check also tries a privileged `lsof` probe without prompting for a password so root-owned listeners are detected before the sandbox build starts. +If a port becomes occupied after preflight but before `openshell forward start` runs, onboarding deletes the just-created sandbox and exits with a retry message instead of leaving a sandbox with an unreachable dashboard URL. When a previous onboard, upgrade, or sandbox crash leaves a stale `openclaw-gateway` host process holding the dashboard port, `nemoclaw onboard --fresh`, `nemoclaw destroy` (when destroying the last sandbox), and `nemoclaw uninstall` automatically sweep the dashboard port range and signal `SIGTERM` then `SIGKILL` to recover. The sweep only targets processes owned by the current user whose command line matches `openclaw-gateway` or `openshell forward` markers, and skips dashboard ports owned by other live sandboxes. @@ -345,7 +347,8 @@ The wizard cleans up stale port forwards and waits for gateway readiness automat ### Colima socket not detected (macOS) Newer Colima versions use the XDG base directory (`~/.config/colima/default/docker.sock`) instead of the legacy path (`~/.colima/default/docker.sock`). -NemoClaw checks both paths. +Some installations expose a top-level Colima socket at `~/.colima/docker.sock`. +NemoClaw checks all three paths. If neither is found, verify that Colima is running: ```console @@ -596,6 +599,8 @@ $ nemoclaw status For local Ollama and local vLLM, `nemoclaw status` also prints an `Inference` line that probes the host-side health endpoint directly. If that line shows `unreachable`, start the local backend first and then retry the request. +For Local Ollama, current releases also print `Inference (auth proxy)` when a proxy token is available. +If the backend is healthy but the auth proxy is `unauthorized` or `unreachable`, re-run onboarding so NemoClaw can recreate the proxy token, restart the proxy, and refresh the route. If the endpoint is correct but requests still fail, check for network policy rules that may block the connection. Then verify the credential and base URL for the provider you selected during onboarding. diff --git a/docs/about/release-notes.md b/docs/about/release-notes.md index 0b1cf8ef3c..23d04140d7 100644 --- a/docs/about/release-notes.md +++ b/docs/about/release-notes.md @@ -24,6 +24,20 @@ status: published NVIDIA NemoClaw is available in early preview starting March 16, 2026. Use this page to track changes. +## v0.0.42 + +NemoClaw v0.0.42 improves onboarding, status diagnostics, local inference checks, and messaging setup: + +- `nemoclaw onboard` uses the Docker-driver OpenShell gateway path on macOS and no longer requires VM driver helper assets for standard macOS onboarding. +- Dashboard port selection probes occupied ports more thoroughly, including root-owned listeners on macOS, and rolls back a newly-created sandbox if the dashboard forward cannot start after the image build. +- `nemoclaw status` shows `Inference` and `Connected` fields for each listed sandbox, and cloudflared service output now distinguishes stopped, invalid PID file, and stale PID states with a `nemoclaw tunnel start` recovery hint. +- Local Ollama status and doctor checks now probe the authenticated proxy in addition to the backend, so a broken proxy is reported separately from a healthy `127.0.0.1:11434` backend. +- Compatible OpenAI endpoint validation retries reasoning-only smoke responses with a larger output budget before classifying the setup as a model output budget problem instead of a route failure. +- `channels add` and `channels remove` normalize channel names before saving or rebuilding, and `channels add` hints when a matching built-in policy preset exists but is not applied yet. +- GPU recovery and uninstall output now use registry-aware recovery commands and clearer gateway removal wording. +- Onboarding applies selected built-in policy presets in a single policy update when possible, while preserving the final live policy and registry state. +- The installer handles unchanged user-local CLI shims idempotently, avoiding duplicate shim-creation messages during install-plus-verify flows. + ## v0.0.41 NemoClaw v0.0.41 improves Docker-driver onboarding and release compatibility: diff --git a/docs/get-started/prerequisites.md b/docs/get-started/prerequisites.md index c6c27cd4dd..06c4704077 100644 --- a/docs/get-started/prerequisites.md +++ b/docs/get-started/prerequisites.md @@ -46,8 +46,12 @@ The sandbox image is approximately 2.4 GB compressed. During image push, the Doc On Linux, the installer can install Docker, start the Docker service, and add your user to the `docker` group. If the group change is not active in the current shell, the installer exits with `newgrp docker` guidance before it starts onboarding. If you choose the native Linux Ollama install path, the onboard wizard also requires `zstd` for Ollama archive extraction. + On Debian and Ubuntu, NemoClaw installs `zstd` with `apt-get` if it is missing; on other Linux distributions, install `zstd` before onboarding. +On macOS, NemoClaw uses the Docker-driver OpenShell gateway path with Docker Desktop or Colima. +You do not need to install or sign a separate OpenShell VM driver helper for standard macOS onboarding. + :::{warning} OpenShell Lifecycle For NemoClaw-managed environments, use `nemoclaw onboard` when you need to create or recreate the OpenShell gateway or sandbox. Avoid `openshell self-update`, `npm update -g openshell`, `openshell gateway start --recreate`, or `openshell sandbox create` directly unless you intend to manage OpenShell separately and then rerun `nemoclaw onboard`. diff --git a/docs/get-started/quickstart.md b/docs/get-started/quickstart.md index 5ed53ef0c0..10d485c503 100644 --- a/docs/get-started/quickstart.md +++ b/docs/get-started/quickstart.md @@ -57,6 +57,8 @@ On Linux, the installer checks Docker before it installs NemoClaw. If Docker is missing, the installer downloads the official Docker convenience script, asks for `sudo`, installs Docker, and starts the Docker service when systemd is available. If Docker is installed but your current shell cannot use the Docker socket yet, the installer adds your user to the `docker` group when needed and exits with a recovery command. +On macOS, the installer uses the Docker-driver OpenShell gateway path with Docker Desktop or Colima. + ```console $ newgrp docker $ curl -fsSL https://www.nvidia.com/nemoclaw.sh | bash @@ -340,6 +342,7 @@ You can chat with the agent from the terminal or the browser. The onboard wizard starts a background port forward to the sandbox dashboard, then prints the dashboard URL in the install summary. The default host port is `18789`. If that port is already taken, NemoClaw uses the next free dashboard port, such as `18790`, and prints that port in the final URL. +If the chosen port becomes occupied after the sandbox build starts, onboarding rolls back the newly-created sandbox and asks you to retry instead of printing an unreachable dashboard URL. The gateway token is redacted from displayed output; retrieve it explicitly when the browser asks for authentication. ```text diff --git a/docs/inference/use-local-inference.md b/docs/inference/use-local-inference.md index ed5ec8507e..e77a51b560 100644 --- a/docs/inference/use-local-inference.md +++ b/docs/inference/use-local-inference.md @@ -188,6 +188,8 @@ If your server does not require authentication, enter any non-empty string (for NemoClaw validates the endpoint by sending a test inference request before continuing. The wizard probes `/v1/chat/completions` by default for the compatible-endpoint provider. If you set `NEMOCLAW_PREFERRED_API=openai-responses`, NemoClaw probes `/v1/responses` instead and only selects it when the response includes the streaming events OpenClaw requires. +If a reasoning model returns only reasoning content before producing a final answer, NemoClaw retries the smoke request with a larger response budget. +Route, configuration, and authentication failures still fail immediately. ### Non-Interactive Setup @@ -364,6 +366,8 @@ $ nemoclaw status ``` The output shows the provider label (for example, "Local vLLM" or "Other OpenAI-compatible endpoint") and the active model. +For Local Ollama, status also checks the authenticated proxy when a proxy token is available. +If `Inference` is healthy but `Inference (auth proxy)` is not, rerun onboarding to repair the proxy path that sandbox requests use. ## Switch Models at Runtime diff --git a/docs/manage-sandboxes/messaging-channels.md b/docs/manage-sandboxes/messaging-channels.md index faf189ceb6..a892ca2896 100644 --- a/docs/manage-sandboxes/messaging-channels.md +++ b/docs/manage-sandboxes/messaging-channels.md @@ -108,6 +108,8 @@ $ nemoclaw my-assistant channels add slack ``` `channels add` prompts for missing credentials, registers the bridge with the OpenShell gateway, updates the sandbox registry, and asks whether to rebuild immediately. +The command accepts mixed-case input such as `Telegram`, then stores and prints the canonical lowercase channel name. +If the matching built-in network policy preset exists but is not applied yet, the command prints a `policy-add ` hint after it registers the channel. Choose the rebuild so the running sandbox image picks up the new channel. If you need optional channel settings such as `TELEGRAM_ALLOWED_IDS`, `TELEGRAM_REQUIRE_MENTION`, `DISCORD_SERVER_ID`, `DISCORD_USER_ID`, or `DISCORD_REQUIRE_MENTION`, export them before the rebuild starts. If you defer the rebuild, apply the change later: diff --git a/docs/project.json b/docs/project.json index 7def5ed20c..2746dbe5e3 100644 --- a/docs/project.json +++ b/docs/project.json @@ -1 +1 @@ -{"name": "nemoclaw", "version": "0.0.41"} +{"name": "nemoclaw", "version": "0.0.42"} diff --git a/docs/reference/commands.md b/docs/reference/commands.md index bee9d5912a..0a774fec1e 100644 --- a/docs/reference/commands.md +++ b/docs/reference/commands.md @@ -360,7 +360,12 @@ The command probes every inference provider and reports one of three states on t Local providers (Ollama, vLLM) probe the host-side health endpoint. Remote providers (NVIDIA Endpoints, OpenAI, Anthropic, Gemini) use a lightweight reachability check; any HTTP response, including `401` or `403`, counts as reachable. No API keys are sent. + +For Local Ollama, the command also probes the authenticated proxy and prints an `Inference (auth proxy)` line when a proxy token is available. +Use that line to distinguish a healthy backend from a broken proxy path that the sandbox uses for inference. + For cloud-only providers, the output omits the NIM status line unless a NIM container is registered or an unexpected NIM container is running. + If the sandbox or gateway cannot be verified, the command exits non-zero instead of reporting healthy inference from stale registry state. Gateway and dashboard health checks treat HTTP `401` from device auth as a live service, not as an offline gateway. @@ -596,6 +601,8 @@ $ nemoclaw my-assistant channels list Store credentials for a messaging channel (`telegram`, `discord`, or `slack`) and rebuild the sandbox so the image picks up the new channel. The command prompts for any missing token, registers it with the OpenShell gateway, then asks whether to rebuild immediately. Running `add` for an already-configured channel simply overwrites the stored tokens — the operation is idempotent. +Channel names are trimmed and lowercased before NemoClaw stores credentials, names bridge providers, or prints rebuild messages. +After a successful add, NemoClaw prints a `policy-add ` hint when a matching built-in network policy preset exists but is not applied to the sandbox yet. ```console $ nemoclaw my-assistant channels add telegram @@ -914,6 +921,7 @@ This command remains as a compatibility alias to `nemoclaw tunnel stop`. Show the sandbox list and the status of host auxiliary services (for example cloudflared). Pass `--json` for machine-readable output with registered sandboxes, service state, inference routes, and messaging health. +For each listed sandbox, the text output includes the configured inference provider and model plus whether an active SSH session is connected. ```console $ nemoclaw status @@ -925,6 +933,7 @@ The command suggests `openshell gateway start --name nemoclaw` or `nemoclaw onbo It exits with code `1` so shell scripts and CI can detect the degraded state from `$?`. For `--json`, the structured output includes `gatewayHealth`, and the exit code is set after the report is generated. A clean machine with no registered sandboxes keeps the legacy `0` exit because no gateway is expected to be configured yet. +If cloudflared is installed but not running, the host-service section reports whether the PID file is missing, invalid, or points at a dead process, then suggests `nemoclaw tunnel start` as the recovery command. ### `nemoclaw inference get` diff --git a/docs/reference/troubleshooting.md b/docs/reference/troubleshooting.md index 0ca467f324..f705ec0ff7 100644 --- a/docs/reference/troubleshooting.md +++ b/docs/reference/troubleshooting.md @@ -174,6 +174,9 @@ The NemoClaw dashboard uses port `18789` by default and the gateway uses port `8 If another sandbox already owns the dashboard port, onboarding scans ports `18789` through `18799` and uses the next free port. If all ports in that range are occupied, the error lists the owner for each port and suggests using `--control-ui-port` with a port outside the range. +On macOS, the port check also tries a privileged `lsof` probe without prompting for a password so root-owned listeners are detected before the sandbox build starts. +If a port becomes occupied after preflight but before `openshell forward start` runs, onboarding deletes the just-created sandbox and exits with a retry message instead of leaving a sandbox with an unreachable dashboard URL. + When a previous onboard, upgrade, or sandbox crash leaves a stale `openclaw-gateway` host process holding the dashboard port, `nemoclaw onboard --fresh`, `nemoclaw destroy` (when destroying the last sandbox), and `nemoclaw uninstall` automatically sweep the dashboard port range and signal `SIGTERM` then `SIGKILL` to recover. The sweep only targets processes owned by the current user whose command line matches `openclaw-gateway` or `openshell forward` markers, and skips dashboard ports owned by other live sandboxes. @@ -371,7 +374,8 @@ The wizard cleans up stale port forwards and waits for gateway readiness automat ### Colima socket not detected (macOS) Newer Colima versions use the XDG base directory (`~/.config/colima/default/docker.sock`) instead of the legacy path (`~/.colima/default/docker.sock`). -NemoClaw checks both paths. +Some installations expose a top-level Colima socket at `~/.colima/docker.sock`. +NemoClaw checks all three paths. If neither is found, verify that Colima is running: ```console @@ -626,6 +630,8 @@ $ nemoclaw status For local Ollama and local vLLM, `nemoclaw status` also prints an `Inference` line that probes the host-side health endpoint directly. If that line shows `unreachable`, start the local backend first and then retry the request. +For Local Ollama, current releases also print `Inference (auth proxy)` when a proxy token is available. +If the backend is healthy but the auth proxy is `unauthorized` or `unreachable`, re-run onboarding so NemoClaw can recreate the proxy token, restart the proxy, and refresh the route. If the endpoint is correct but requests still fail, check for network policy rules that may block the connection. Then verify the credential and base URL for the provider you selected during onboarding. diff --git a/docs/versions1.json b/docs/versions1.json index 0f14e86323..ae54736939 100644 --- a/docs/versions1.json +++ b/docs/versions1.json @@ -1,6 +1,10 @@ [ { "preferred": true, + "version": "0.0.42", + "url": "https://docs.nvidia.com/nemoclaw/0.0.42/" + }, + { "version": "0.0.41", "url": "https://docs.nvidia.com/nemoclaw/0.0.41/" },