NemoClaw for Pi CLI Commands Reference
Use nemoclaw for Pi sandbox lifecycle and pi for work inside the sandbox.
Pi remains a release candidate. Ordinary installations reject --agent pi until final activation lands in a release. Internal candidate qualification settings are not user commands.
Onboard and Inspect
Run Pi
Inside a connected sandbox:
--no-approve ignores project-local executable resources.
It does not disable AGENTS.md or CLAUDE.md.
Use --no-context-files when project instructions must not enter the prompt.
Configure Model Metadata
Set supported Pi model metadata before onboarding or a fresh replacement.
Pi supports a positive NEMOCLAW_CONTEXT_WINDOW no larger than 4194304, a NEMOCLAW_MAX_TOKENS value from 1 to 1000000000, and true or false for NEMOCLAW_REASONING. It does not support NEMOCLAW_REASONING_EFFORT or the runtime inference set command. A normal rebuild replays the recorded values.
Preserve and Replace State
OpenShell preserves Pi’s complete native home and workspace through stop, start, and reconnect. Finish active Pi work before rebuilding; an unavoidable rebuild transfers the complete native state to the replacement sandbox.
Rebuild validates recorded authority and selects the immutable Pi image authorised by the protected qualification receipt.
Update the Host and Sandbox
After updating NemoClaw, inspect registered sandboxes before rebuilding Pi.
The host update does not self-update Pi inside a running sandbox. While Pi remains a candidate, rebuild uses the protected qualification receipt rather than the installed release catalogue.
Stop or Remove the Sandbox
Copy any state you need before destroy. Destroy removes the OpenShell sandbox storage, but does not remove a provider credential from the OpenShell gateway.
After every dependent sandbox is gone, remove the gateway-held credential explicitly.