VDR 5 checklist: non-DGX findings and current-release verification

This issue reconciles the non-DGX findings in Will Curran's July 8, 2026 VDR 5 progress update.

DGX Spark and DGX Station are tracked separately in #6743. This checklist covers Getting Started, New NemoClaw Setup, Local Models, Windows WSL + RTX, Brev, and the reference-only macOS, OpenClaw plugin, WSL2 ARM/N1X, Jetson, and migration findings.

The original evidence spans older releases, especially v0.0.55 and WSL v0.0.61. As of July 20, 2026, the newest semver tag is v0.0.88, and the maintained lkg tag points to the same commit. Verification should use the maintained current release available when each item is tested.

Status and validation rules

Every item begins unchecked, including items with related closed issues or merged PRs.

[ ] means the exact VDR behavior still needs current-release reconciliation.
Check an item only when the original behavior passes on the affected platform, code and tests directly cover it, or a maintainer records that it is no longer applicable or intentionally declined.
A related closed issue or merged PR is evidence of progress, not by itself proof that the VDR finding is resolved.
Record the tested release, platform, commands, result, and evidence when checking an item.
macOS, plugin, N1X, Jetson, and migration were not rated or were descoped. Their presence here does not approve them as supported NemoClaw product surfaces.

Getting Started

Verify public installer and release trust. The public one-line installer previously resolved to v0.0.55 while newer maintained builds existed. On a clean supported host, capture the resolved ref and nemoclaw --version; confirm they match the maintained lkg, the completion output exposes the installed version, and an explicit NEMOCLAW_INSTALL_TAG=<tag> pin works. Related: #4891, #5630, PR #5545. lkg is intentionally admin-promoted and may trail newest semver, so acceptance is maintained-channel trust rather than requiring lkg == latest.
Verify one authoritative first-time prerequisite path. Users previously had to assemble Node.js, Docker, OpenShell, and platform preparation requirements from README and platform pages. Starting from the product page and README, confirm the main journey identifies mandatory prerequisites before expensive work and links to platform-specific preparation without conflicting instructions. Related: #1403, #4630, PR #5616.
Verify the public NVIDIA product page links directly to canonical documentation. Confirm a new user can reach a current installation or Quickstart page without first navigating through GitHub. No exact tracker proving the external product-page route was found.
Verify the host, sandbox, and two-terminal workflow. Quickstart must state where each command runs and explain that openshell term is a separate host terminal used for network approvals. Confirm the user can approve or deny and return to the original workflow. Related: #5082.
Verify remote/dashboard discoverability. Complete onboarding over SSH and confirm completion output gives the local URL and copyable SSH forwarding command, the URL can be reprinted later, and Quickstart links to remote-dashboard guidance. Related: #20, #5084, #5925.
Verify custom endpoint and policy usability. Add, list, update, and remove a custom HTTPS endpoint through supported NemoClaw surfaces. Errors must identify invalid fields and show valid examples; docs must distinguish temporary approval from persistent policy. Related: #2039, #2867, #5764, #991, #3590, #4510, and open #7178.

New NemoClaw Setup

Verify interrupted public-install recovery. Interrupt before sandbox-name capture, after provider selection, and after sandbox creation. Rerunning must resume safely or print one valid --fresh recovery path without silently reusing an unrelated provider or sandbox. Related: #5627, #5719, #5720, PR #5487, PR #5642, PR #5690.
Verify resume preserves completed choices. Interrupt after each onboarding section and confirm nemoclaw onboard --resume does not repeat sandbox-name, web-search, messaging, resource-profile, or other completed non-secret choices. Raw credentials must not be persisted. Related exact tracker: #6932.
Verify default security/status messages are honest. On a fresh sandbox, run status, doctor, TUI, and OpenClaw security audit. Expected NemoClaw-managed defaults must not be presented as user misconfiguration, while actionable security failures remain prominent. Related: PR #5474, PR #5477, #3271.
Verify gateway lifecycle and ownership. Start, stop, restart, destroy, reboot, and re-onboard. One component must clearly own the OpenShell gateway; commands must explain what stops, what remains, and how ports are released or recovered. Related open work: #6576, #6903, #7174; improvements: PR #5181, PR #5382.
Remaining work: OpenShell persist after host reboot Install and uninstall a managed OpenShell gateway service for reboot persistence #6903
Verify displayed prompt defaults. Press Enter at provider, resource-profile, messaging, policy, and confirmation prompts. Empty input must select the displayed default; prompts without defaults must explain what is required. Related: #4432, #4387, #5557.
Verify host/sandbox file movement is discoverable and works. Find the NemoClaw upload, download, and sessions export commands through help/docs; confirm relative host paths resolve from the caller working directory and routine file movement does not require raw OpenShell commands. Related: PR #5201, PR #5509, #2631, #1045.

Local Models

Reproduce the WSL Local Ollama full agent loop. Installation previously completed with green checks but the agent produced no reply and could show auto compaction could not recover this turn. Test supported Windows-host and WSL-hosted Ollama paths through TUI and dashboard, and require failures to identify Ollama, auth proxy, inference.local, model, or OpenClaw. Related: #336, #1472, #2770, #4421, PR #5508; related but non-identical open ARM64 case #3707.
Verify express default model sizing. WSL express previously attempted llama3.3:70b, too large for the default machine. Confirm the default fits detected RAM/GPU/architecture, larger models require explicit choice, and size/headroom appears before download. Related: #2639, open #3707.
Verify llama.cpp through the generic OpenAI-compatible path. Start a documented llama.cpp server, ensure onboarding does not misclassify it as vLLM, complete sandbox creation, and send inference from inside the sandbox. Failures must distinguish schema, model ID, reachability, and compatibility. Related: PR #5400, #5635, #5636, #5744. No exact llama.cpp E2E tracker was found.
Verify the installed OpenClaw version contract. A new sandbox must match the OpenClaw version pinned by its NemoClaw release. Docs must explain that supported means the release pin, not necessarily upstream npm latest. Related: #2635 and the disposition in #6743.

Windows WSL + RTX

This was the highest-risk non-DGX row. The evidence was from WSL v0.0.61, not only stale .55 behavior.

Brev

Quickstart explicitly separates host provisioning, NemoClaw installation, onboarding, and sandbox creation. Users must not assume a sandbox exists when the Brev instance becomes ready. Related: #5084, PR #5247.
Pressing Enter accepts the displayed Brev resource-profile default. Related: #4432, #4387, #5557.
Explain or remove port assignment before any sandbox exists. Determine whether it belongs to a gateway, future forward, or stale resource; the UI must not imply a sandbox is already running. No exact tracker found.
Measure the reported 8–10 minute Brev sandbox creation. Separate image pull, container creation, gateway, OpenClaw, inference validation, and dashboard delivery for cold and warm instances. Related: #2001, #1326, #1328, #1329.
Reproduce Brev streaming latency. Compare direct provider time-to-first-token with NemoClaw gateway/router/sandbox/TUI delivery and prove tokens stream instead of buffering. Related: #2001; no exact current tracker found.
Previous TUI messages remain visible across scroll, reconnect, restart, and dashboard/TUI switching. Related: #2603, #3145.
Run a clean current-release Brev golden-path validation. Provision the documented SKU; install, onboard, infer, open dashboard, reconnect, stop/restart, and destroy; record version, SKU, durations, and failures. Related: #2634, #2425, open #6576, #6404.

Reference-only findings requiring a scope decision

Checking an item below may mean verified, moved into an accepted scoped issue, or explicitly retained out of scope.

macOS — VDR 5 descoped

OpenClaw plugin — not rated and descoped

~~Record a maintainer product-scope decision defining ownership, lifecycle, compatibility, security, and validation before treating the in-sandbox plugin as supported.~~
~~If accepted, verify openclaw nemoclaw discovery and registration inside the sandbox; VDR returned unknown command 'nemoclaw'.~~
~~Explain host nemoclaw and in-sandbox plugin as distinct paths with explicit state ownership.~~
~~Define OpenShell gateway vs OpenClaw/plugin gateway startup order and lifecycle authority.~~
~~Synchronize plugin status with actual sandbox and inference state; do not report not running/configured while the system works.~~
~~Replace stale build-time inference banner/config with current provider state.~~
~~Define actionable /nemoclaw slash commands if this surface is supported.~~

~~No accepted issue was found that re-establishes this plugin as a supported product surface.~~

WSL2 ARM / N1X — not rated

Record availability, artifact source, versioning, installation, security-update, and external-user support for the special ARM Ollama builds used in VDR testing.
Decide whether full N1X validation is supported scope; if accepted, define OS, hardware, Ollama build, model, performance target, validation owner, and E2E coverage. Related but non-comprehensive open issue: #3707.

Jetson — VDR 5 descoped

Make unsupported-JetPack warning state concrete implications, supported alternatives, and whether onboarding should continue.
Verify default config emits no irrelevant qqbot warning. Related: #6000.
Ensure CLI is immediately on PATH or print clean refresh commands without $. Related: #2868, #4754, PR #5045.
Improve progress visibility for the reported approximately 17-minute install.
~~Offer explicit None / No messaging channels. Related: #3471.~~
Give an immediate first-chat handoff with supported connect/TUI commands and where they run. Related: #755.
Verify current Jetson GPU detection/passthrough E2E coverage. Related: PR #5613.

Existing OpenClaw migration — descoped

~~Record a product-scope decision covering ownership, compatibility, secrets, rollback, extensions, sessions, and lifecycle.~~
~~If accepted, implement and verify non-dry-run blueprint acquisition; VDR dry-run succeeded but real migration failed because fetchBlueprint was unimplemented.~~
~~If accepted, verify plugin discovery before offering openclaw nemoclaw migrate.~~
~~If accepted, document a safe fallback/manual path for configuration, sessions, extensions, and hooks.~~

~~No accepted migration issue or design decision establishing this supported surface was found.~~

Completion evidence

Every checked item links to current-release evidence, an exact fixing PR/test, or an explicit maintainer disposition.
Platform-specific findings record OS, architecture, hardware, container runtime, inference provider, and release.
Related improvements are not treated as proof unless they cover the original reproduction.
Descoped sections have explicit scope decisions and are not documented as supported accidentally.
Remaining actionable failures have dedicated issues with owners and acceptance criteria.
Duplicate findings point to one canonical issue.
Final summary distinguishes fixed, verified, not reproducible, duplicate, declined, descoped, and still open.

[Getting Started]
Verify remote/dashboard discoverability - resolved

Fixed by #5929 (fixes #5925) in v0.0.78; code + unit tests present on current v0.0.88:

Onboard output appends a copy-paste SSH forward hint when run inside an SSH session with the dashboard on loopback — reprintable via nemoclaw <sandbox> dashboard-url.
Quickstart (docs/get-started/quickstart.mdx) documents the ssh -L <port>:127.0.0.1:<port> <user>@<host> command and cross-links Remote Dashboard Access.

Platform-independent by construction — gated on SSH_CONNECTION, no platform branch (ssh-forward-hint.ts; unit tests assert the output), so it holds on any non-DGX remote host. Ready-summary output:

  Remote access (SSH session detected):
    On your workstation, run:
      ssh -L 18790:127.0.0.1:18790 name@<host>
    Then open the dashboard URL above in your local browser.

<user> auto-fills; <host> is a placeholder by design (SSH_CONNECTION can't recover a ~/.ssh/config alias, -p, or ProxyJump). Related #20 (reachable bind + device-auth) and #5084 (remote-GPU doc) both closed.

[Getting Started]
Verify custom endpoint and policy usability - resolved

Custom-endpoint CRUD works through NemoClaw surfaces; no drop to raw openshell needed:

Add — policy-add takes built-in presets and custom YAML via --from-file ([CLI] nemoclaw policy-add has no custom-preset surface; custom egress targets require dropping to openshell policy set #2039); generated policy carries the required version field ([Linux] nemoclaw policy-add fails: missing version field in generated policy YAML #991).
List — policy-list reflects applied custom presets accurately in policy-list and status (policy-list reports custom preset as inactive while active policy enforces it #3590, [Ubuntu 24.04][Policy] policy-add --from-file exits 0 but custom preset is absent from policy-list and status #4510).
Update — change a custom preset by remove + re-add (policy-add no-ops on an already-applied preset); custom inference endpoints re-point via nemoclaw inference set.
Remove — policy-remove removes applied/custom presets.
Errors — invalid policy YAML now fails with the specific missing field rather than a raw parse dump ([Linux] nemoclaw policy-add fails: missing version field in generated policy YAML #991).
Docs — reference/network-policies.mdx distinguishes temporary session approval ("added to the running policy for the session") from persistent policy (baseline + presets); customize-network-policy.mdx round-trip fixed ([All Platforms][Docs] NemoClaw Customize Network Policy — openshell policy set command fails as documented #5764); guided integration examples added (VDR 4: Common integration policy setup lacks guided examples #2867).

Out of scope for this item: #7178 tracks persistent exclusion of a built-in baseline entry (a distinct capability, accepting reduced support) — not custom-endpoint removal — so it does not gate this item.

[Getting Started]
Verify one authoritative first-time prerequisite path — resolved

Verified on 2026-07-22:

The README directs first-time users to the canonical Prerequisites page before the agent-specific Quickstarts.
Prerequisites consolidates hardware minimums, Node.js, npm, Docker, the OpenShell lifecycle, platform status, and required Windows and DGX Station preparation.
Quickstart repeats “Review the Prerequisites before you begin” before its install procedure.
Platform support is generated from the canonical ci/platform-matrix.json, keeping setup guidance and support claims aligned.
The product page’s direct installer is intentional and relies on installer preflight. Direct product-page documentation routing is tracked separately by the next VDR checklist item.

No conflicting supported-platform prerequisite instructions were found. #1403 and #4630 are relevant supporting work. PR #5616 updates architecture references and is not prerequisite-path evidence.

[Getting Started]
Direct product-page link to canonical documentation — intentionally declined

Maintainer disposition on 2026-07-22: keep the current product-page journey by design.

The NVIDIA NemoClaw product page is intentionally install-first: it provides agent-specific installer commands and Brev “Try It Now” paths. Users who choose the repository route reach the canonical NemoClaw documentation, prerequisites, and Quickstarts from the README.

A separate direct product-page link to a NemoClaw Quickstart is not required for this journey, and no external product-page change is requested. Closing this checklist item as intentionally declined rather than verified.

[Getting Started]
Host, sandbox, and two-terminal workflow — intentionally declined as a Quickstart requirement

Maintainer disposition on 2026-07-22: keep the current documentation split by design.

The Quickstart should remain focused on installation, onboarding, sandbox connection, and the first agent prompt. The detailed network-approval workflow belongs on the dedicated Approve or Deny Agent Network Requests page.

That page now documents the host context, local and remote openshell term paths, sandbox selection, approve and reject controls, and session persistence. #5082 was verified and closed for those corrections. A second terminal is an optional convenience when keeping the agent TUI open, not a mandatory Quickstart step.

Closing this checklist item as intentionally declined by design rather than requiring the approval procedure to be duplicated in Quickstart.

Verified interrupted public-install recovery by direct automated coverage on 2026-07-22.

Maintained reference: lkg = v0.0.90. Verification platform: Darwin arm64 using the repository test harness.

Evidence:

Before sandbox-name capture: test/install-onboard-yes.test.ts confirms an in-progress session with no sandbox and a pending sandbox step restarts with --fresh, not --resume.
After provider selection: the saved-session fixture records provider selection/inference complete with no sandbox and a pending sandbox step, which maps to the same safe pre-sandbox recovery path. test/onboard-resume-provider-recovery.test.ts also confirms current or explicit provider selection wins without silently recovering a provider from an unrelated sandbox.
After sandbox creation: test/install-onboard-yes.test.ts confirms a completed sandbox with its recorded name restarts with --resume, not --fresh.
Invalid partial states, including a name without a completed sandbox step and a completed step without a name, fall back to --fresh.

Focused commands and results:

npx vitest run --project integration test/install-onboard-yes.test.ts test/onboard-resume-provider-recovery.test.ts test/onboard-sandbox-name.test.ts — 61 passed.
npx vitest run --project cli src/lib/onboard/entry-options.test.ts src/lib/onboard/session-bootstrap.test.ts — 27 passed.

Total: 88 passed, 0 failed. No manual three-point Ctrl-C run through the public installer was performed; this item is checked under the issue validation rule allowing direct code and test coverage.

Closed by current Brev UX validation and maintainer disposition.

Observed long-form TUI response:

prompt submitted: t=0s
first visible text: t=6s
response complete: t=27s
visible output window: 21s

The long response appeared progressively during that window, so end-of-response buffering was not observed. The reviewer judged the response speed acceptable for the response length, and the original poor-streaming experience did not reproduce.

A direct-provider TTFT comparison and token-level trace were not captured. This closes the VDR reconciliation as a current-UX/not-reproduced disposition, not as a general performance benchmark or numeric latency guarantee. No dedicated defect tracker is needed from this observation.

Closed by current Brev validation.

Verified behavior:

messages remain visible when scrolling away and back within the same session;
the same session retains its history after exiting, reconnecting, and restarting the TUI;
dashboard and TUI show the same conversation when both select the same session;
different sessions remain isolated and do not inherit one another’s history;
returning to the original session restores its history.

This matches the intended session-scoped history contract. The historical disappearing/duplicate/out-of-order behavior is tracked by #2603 and #3145, both closed after the OpenClaw upgrade, with regression coverage from PR #3364. The VDR behavior did not reproduce in this Brev validation.

Closed by clean maintained-channel Brev validation.

Environment:

Brev instance: nemoclaw-840b8d
Brev machine/SKU: n2d-standard-4 (CPU)
NemoClaw: v0.0.90
Maintained-channel check: v0.0.90 resolves to commit acfa2613c7a645ae1bff21914f25d824e5fbcf62, the current lkg commit at validation time
OpenClaw: 2026.6.10 (aa69b12)
Sandbox: my-assistant
Provider/model: inference/nvidia/nemotron-3-super-120b-a12b

Tester confirmed the complete path passed: provision, install, onboard, inference, dashboard, reconnect, lifecycle recovery, and destroy.

Captured lifecycle evidence:

nemoclaw my-assistant recover confirmed the OpenClaw gateway was running.
nemoclaw my-assistant stop stopped the in-sandbox gateway and container while preserving workspace state; docker ps was empty and docker ps -a showed the stopped sandbox container.
The CLI has no literal restart action and reported the valid lifecycle actions. The supported restart sequence is stop followed by start.
nemoclaw my-assistant start returned the sandbox to Ready in 3 seconds and recovered the OpenClaw gateway.
Reconnect succeeded, the TUI retained the existing main session, and a new prompt received a valid response.

Timing record: stop/start readiness was 3 seconds. Exact provision, install, onboard, dashboard, reconnect, inference-completion, and destroy durations were not captured in this manual run. No blocking product failure reproduced; the unsupported literal restart command was handled by the documented stop/start lifecycle. Broader automated image qualification and gateway-authority work remains tracked separately in #6409, #6943, #6576, and #6404.

Closed as documented cosmetic behavior in the macOS reference-only/descoped section.

VDR #5 reported zsh autocorrect noise such as suggesting .nemoclaw when invoking nemoclaw. This is shell-level behavior: when zsh cannot resolve the nemoclaw executable on PATH, the existing ~/.nemoclaw directory becomes a plausible correction candidate.

Current generic troubleshooting documents the underlying recovery:

reload the shell profile with source ~/.zshrc or open a new terminal;
when the managed shim is under ~/.local/bin/nemoclaw, add ~/.local/bin to PATH if the command is still unresolved.

Repository issue searches found no exact tracker for this cosmetic prompt. No separate product fix is prioritized, and this disposition does not re-establish macOS as a supported VDR #5 surface.

Closed by maintainer disposition in the macOS reference-only/descoped section.

The reported duplicate was the phrase license and and third-party software notice. Exact tracker #7301 was fixed by merged PR #7306, which changed the prompt to license and third-party software notice and added a regression assertion against adjacent duplicated words. #7302 was a duplicate report.

The consent contract intentionally requires the full word yes; Enter, n, no, and other input decline without recording acceptance. The separate UX question for a bare y—whether to provide a recovery hint while retaining explicit full-word consent—remains independently tracked in open #7469 and PR #7471. It does not block closure of this cosmetic, descoped macOS reference item and remains visible as a child issue of #7209.

[macOS]
Verify dashboard reachability does not depend on first prompting the TUI - resolved
Resolved a while ago — the Dashboard Delivery Contract (#2390, PR #2398 merged 2026-04-24, closed 2026-05-06) made dashboard reachability a first-class concern established at onboard time, independent of the TUI. Present on current v0.0.88:

Forward set up during onboarding — ensureDashboardForward (src/lib/onboard/agent-dashboard-forward.ts) establishes the dashboard port forward and CHAT_UI_URL as part of onboarding, not lazily on first TUI open; reachability (port, CORS origins, health, authenticated URL) derives from a single contract (dashboard-access.ts).
URL delivered without the TUI — the "OpenClaw is ready" completion block prints the dashboard URL and nemoclaw <sandbox> dashboard-url reprints it, so the dashboard is reachable directly.

Dashboard-before-first-prompt validation confirmed by teammate testing: after onboarding, the dashboard was opened and was reachable before launching the TUI or submitting any TUI prompt. The historical behavior where dashboard reachability appeared only after the first chat prompt did not reproduce. This supports the already-checked reference-only item; #2390 remains related architectural evidence.

Verified two cases for Local Models:

QA verification — NemoClaw v0.0.93, WSL2 x86_64 (Ubuntu 24.04, RTX PRO 6000 Blackwell Server 97 GB / 95.3 GiB VRAM)

Check	Result
Default model fits detected RAM/GPU/arch	✅ PASS — default is qwen3.6:35b (23 GB, ~20 GB VRAM) on 95 GB GPU; 73 GB headroom. No longer llama3.3:70b.
Larger models require explicit choice	✅ PASS — wizard shows numbered list; no auto-download without selection
Size/headroom appears before download	❌ FAIL — wizard shows model names only; no file size, VRAM requirement, or headroom displayed - #7479

feat(gateway): manage the default gateway service (#7319)

QA verification — Jetson section (NemoClaw v0.0.93, JetPack 6.2 IGX Orin)

Verified the 6 in-scope Jetson items (the qqbot item / #6000 is struck through / descoped — not verified). Status:

✅ CLI immediately on PATH or clean refresh commands without $ (Related #2868, #4754, PR #5045) — Installer prints Verified: nemoclaw is available at ~/.local/bin/nemoclaw plus refresh commands with no leading $ (export PATH="…/.local/bin:$PATH", source "…/nvm.sh" && nvm use 22). PASS.

✅ Progress visibility for the ~17-min install — Step markers [1/3]…[3/3] and onboard [1/8]…[8/8], streaming docker-layer output, and a live ⏳ Still working on Sandbox creation… (Ns elapsed) counter. PASS.

✅ Explicit None / No messaging channels (Related #3471) — Prompt documents … Enter for current selection, or 'none'; entering none → Skipping messaging channels. PASS.

✅ Immediate first-chat handoff with connect/TUI commands and where they run (Related #755) — Completion prints an "OpenClaw is ready" block: Browser URL + nemoclaw <name> connect → openclaw tui, and (SSH session detected) instructs running ssh -L … on the workstation. PASS.

❌ Jetson GPU detection/passthrough E2E (Related PR #5613) — Detection passes, but the sandbox CUDA proof fails for the non-root sandbox user (cuInit(0)=999, NvRmMemInitNvmap … Permission denied), aborting onboarding. cuInit(0) as root inside the same container returns 0 — device nodes are mounted and libcuda is present, so the plumbing is correct; only the unprivileged sandbox user cannot init CUDA on this IGX Orin. Workaround: NEMOCLAW_SANDBOX_GPU=0 (CPU). Filed → #7610.

⚠️ Unsupported-JetPack warning clarity — On an unrecognized L4T version the installer emits only Jetson detected (L4T X) but version is not recognized — skipping host setup and silently continues; it does not state the implications, the supported versions (JetPack 6 / JP7-R38), or whether onboarding should continue. This box runs supported JP6.2, so assessed from scripts/setup-jetson.sh. Filed → #7612.

Environment: NVIDIA IGX Orin Developer Kit, JetPack 6.2 (L4T R36.5.1), NemoClaw v0.0.93, OpenShell 0.0.85, OpenClaw 2026.7.1.

[WSL + RTX] A supported command reprints the complete OpenClaw is ready block — FAIL

Verified on Windows WSL2 (Ubuntu 24.04), NemoClaw v0.0.95.

Commands tested:

nemoclaw my-assistant dashboard-url — prints authenticated URL only; missing terminal steps and management commands
nemoclaw status — shows sandbox health; not the ready block format
nemoclaw my-assistant status — detailed health/config; not the ready block format
nemoclaw my-assistant ready — Unknown action (v0.0.95)

No supported command reprints all four required elements (Browser URL, terminal steps, authenticated dashboard URL, management commands) without restarting onboarding. The printDashboard() function in the source is only called during onboarding finalization and is not exported for reuse.

Tracked in #7473. Item remains unchecked pending that fix.

[WSL2 ARM / N1X — not rated] Sub-item A + B

Sub-item A — ARM Ollama build info (from #3707):

Artifact source: standard Ollama releases (ollama.com), no special NVIDIA ARM build
Version used in VDR testing: Ollama 0.23.4
Hardware: Windows 11 + WSL2 Ubuntu 24.04 aarch64, NVIDIA JMJWOA-Generic-GPU 64 GB iGPU, driver 592.60 / CUDA 13.1
Installation: standard Windows-host Ollama installer
Security updates: standard Ollama community release cadence
External-user support: standard Ollama community support
NemoClaw-side model-selection issue was addressed by PR fix(inference): mark the Windows-ARM N1X iGPU compute-constrained #6234 in v0.0.74

Sub-item B — Scope decision:
Confirmed with San Dang (2026-07-28): N1X validation is kept out of scope for now and will be revisited if needed.

Navigation Menu

Repository navigation

VDR 5 checklist: non-DGX findings and current-release verification #7209

VDR 5 checklist: non-DGX findings and current-release verification

Status and validation rules

Getting Started

New NemoClaw Setup

Local Models

Windows WSL + RTX

Brev

Reference-only findings requiring a scope decision

macOS — VDR 5 descoped

OpenClaw plugin — not rated and descoped

WSL2 ARM / N1X — not rated

Jetson — VDR 5 descoped

Existing OpenClaw migration — descoped

Completion evidence

24 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

VDR 5 checklist: non-DGX findings and current-release verification #7209

Description

VDR 5 checklist: non-DGX findings and current-release verification

Status and validation rules

Getting Started

New NemoClaw Setup

Local Models

Windows WSL + RTX

Brev

Reference-only findings requiring a scope decision

macOS — VDR 5 descoped

OpenClaw plugin — not rated and descoped

WSL2 ARM / N1X — not rated

Jetson — VDR 5 descoped

Existing OpenClaw migration — descoped

Completion evidence

Activity

hunglp6d commented on Jul 21, 2026

hunglp6d commented on Jul 21, 2026

sandl99 commented on Jul 22, 2026

sandl99 commented on Jul 22, 2026

sandl99 commented on Jul 22, 2026

sandl99 commented on Jul 22, 2026

24 remaining items

sandl99 commented on Jul 24, 2026

sandl99 commented on Jul 24, 2026

sandl99 commented on Jul 24, 2026

sandl99 commented on Jul 24, 2026

sandl99 commented on Jul 24, 2026

hunglp6d commented on Jul 24, 2026

sandl99 commented on Jul 24, 2026

hulynn commented on Jul 24, 2026

wangericnv commented on Jul 27, 2026

lyral-commits commented on Jul 28, 2026

lyral-commits commented on Jul 28, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions