docs: sync NemoClaw registry ownership wording (#45)

Co-authored-by: mmckeen-nv <mmckeen-nv@users.noreply.github.com>
This commit is contained in:
mmckeen-nv
2026-09-05 23:07:34 -07:00
committed by GitHub
co-authored by mmckeen-nv
parent 5f8e30c33e
commit cbbdd1b4d2
3 changed files with 3 additions and 3 deletions
+1 -1
View File
@@ -221,7 +221,7 @@ The dashboard shells out to the OpenShell CLI for several operations:
- `openshell provider create/update/delete/list`
- `openshell inference set/get/update`
The **Quick Deploy New NemoClaw Sandbox** path clones a registered image through OpenShell, but it deliberately does not write the clone into NemoClaw's private `sandboxes.json`. Current NemoClaw entries include lifecycle identity, policy-authority, and workload receipts that must be issued by NemoClaw itself. The clone remains visible and operable through OpenShell Control; use **Fresh NemoClaw Image** when the new sandbox must participate in NemoClaw-managed lifecycle operations.
The **Quick Deploy New NemoClaw Sandbox** path clones a registered image through OpenShell, but it deliberately does not write the clone into NemoClaw's private `sandboxes.json`. Current NemoClaw entries include lifecycle identity, workload provenance, and agent-specific state that must be issued by NemoClaw itself. The clone remains visible and operable through OpenShell Control; use **Fresh NemoClaw Image** when the new sandbox must participate in NemoClaw-managed lifecycle operations.
OpenClaw dashboard access is loopback-only inside the host/sandbox context, so the UI uses local proxy routes: