Summary
The NemoClaw onboarding installer fails at the final step [7/7] when applying policy presets. After accepting the suggested presets (pypi, npm), the installer passes an unexpected mkdir argument to the openshell policy set command, causing it to fail.
Environment
Hardware: NVIDIA DGX Spark (Founders Edition), GB10 Grace Blackwell Superchip, 128GB unified memory
Architecture: aarch64
OS: DGX OS (Ubuntu-based)
OpenShell version: 0.0.6
NemoClaw: Cloned from main branch on 16 March 2026
Node.js: v22.22.1
Steps to Reproduce
Install OpenShell v0.0.6
Clone NemoClaw: git clone https://github.com/NVIDIA/NemoClaw.git
Run cd NemoClaw && ./install.sh
Complete onboarding steps 1–6 successfully (preflight, gateway, inference, sandbox all pass)
At step [7/7] Policy presets, accept the suggested presets by pressing Y
Expected Behaviour
Policy presets are applied to the sandbox and onboarding completes successfully.
Actual Behaviour
The installer fails with:
Apply suggested presets (pypi, npm)? [Y/n/list]: Y
error: unexpected argument 'mkdir' found
Usage: openshell policy set [OPTIONS] --policy [NAME]
For more information, try '--help'.
Command failed (exit 2): openshell policy set --policy "/tmp/nemoclaw-policy-1773697104985.yaml" --wait s
It looks like the install script is passing an extra argument (possibly mkdir or a sandbox name like s) to the openshell policy set command.
Manual Workaround Attempted
The temporary policy file was created successfully at /tmp/nemoclaw-policy-1773697104985.yaml. I tried applying it manually:
openshell policy set --policy /tmp/nemoclaw-policy-*.yaml --wait
This returned a different error:
→ Using sandbox 'sudo' (last used)
Error: × status: InvalidArgument, message: "filesystem policy cannot be removed on a live sandbox",
details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "date":
"Mon, 16 Mar 2026 21:39:24 GMT"} }
Two possible issues with the manual attempt:
It auto-selected a sandbox called "sudo" which doesn't seem correct
It refused to change the filesystem policy on a running sandbox
Additional Context
Steps 1–6 of the onboarding all completed successfully, including GPU detection (1 GPU, 124610 MB VRAM), gateway startup, and sandbox creation.
This was tested on launch day (16 March 2026, GTC announcement).
Related issue filed on OpenShell repo: (add link to your other issue here if you like)
Summary
The NemoClaw onboarding installer fails at the final step [7/7] when applying policy presets. After accepting the suggested presets (pypi, npm), the installer passes an unexpected mkdir argument to the openshell policy set command, causing it to fail.
Environment
Hardware: NVIDIA DGX Spark (Founders Edition), GB10 Grace Blackwell Superchip, 128GB unified memory
Architecture: aarch64
OS: DGX OS (Ubuntu-based)
OpenShell version: 0.0.6
NemoClaw: Cloned from main branch on 16 March 2026
Node.js: v22.22.1
Steps to Reproduce
Install OpenShell v0.0.6
Clone NemoClaw: git clone https://github.com/NVIDIA/NemoClaw.git
Run cd NemoClaw && ./install.sh
Complete onboarding steps 1–6 successfully (preflight, gateway, inference, sandbox all pass)
At step [7/7] Policy presets, accept the suggested presets by pressing Y
Expected Behaviour
Policy presets are applied to the sandbox and onboarding completes successfully.
Actual Behaviour
The installer fails with:
Apply suggested presets (pypi, npm)? [Y/n/list]: Y
error: unexpected argument 'mkdir' found
Usage: openshell policy set [OPTIONS] --policy [NAME]
For more information, try '--help'.
Command failed (exit 2): openshell policy set --policy "/tmp/nemoclaw-policy-1773697104985.yaml" --wait s
It looks like the install script is passing an extra argument (possibly mkdir or a sandbox name like s) to the openshell policy set command.
Manual Workaround Attempted
The temporary policy file was created successfully at /tmp/nemoclaw-policy-1773697104985.yaml. I tried applying it manually:
openshell policy set --policy /tmp/nemoclaw-policy-*.yaml --wait
This returned a different error:
→ Using sandbox 'sudo' (last used)
Error: × status: InvalidArgument, message: "filesystem policy cannot be removed on a live sandbox",
details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "date":
"Mon, 16 Mar 2026 21:39:24 GMT"} }
Two possible issues with the manual attempt:
It auto-selected a sandbox called "sudo" which doesn't seem correct
It refused to change the filesystem policy on a running sandbox
Additional Context
Steps 1–6 of the onboarding all completed successfully, including GPU detection (1 GPU, 124610 MB VRAM), gateway startup, and sandbox creation.
This was tested on launch day (16 March 2026, GTC announcement).
Related issue filed on OpenShell repo: (add link to your other issue here if you like)