nemoclaw-user-reference

The NemoClaw plugin integrates with OpenShell inside a sandbox by routing interactions across host, gateway, sandbox, and provider layers. Blueprint policies define these component interactions to ground development and troubleshooting decisions.

The blueprint layout in NemoClaw defines structural policies for the sandbox, constraining changes to OpenShell and NemoClaw. It maps plugin components to host, gateway, sandbox, and provider interactions to guide safe development.

To set up a NemoClaw sandbox, load the architecture details reference to map plugin components, then apply blueprint policies for policy routing across host, gateway, sandbox, and provider layers to ensure correct configuration.

The deny-by-default network policy is an invariant in NemoClaw blueprint configurations that ensures secure sandbox isolation. It restricts unauthorized network access unless explicitly allowed, safeguarding credential handling and provider interactions.

You can extend the NemoClaw plugin structure by constraining changes to OpenShell and NemoClaw according to blueprint policies. Verify invariants like deny-by-default network policy and credential handling to ensure safe modifications.

The best way to debug NemoClaw and OpenShell interactions is to map components to host, gateway, sandbox, and provider layers using the architecture reference. This grounds troubleshooting by identifying where interactions fail within the stack.