Description
docs/reference/cli-selection-guide.md still recommends openshell sandbox exec as the primary one-off in-sandbox command and does not document nemoclaw <name> exec as the recommended path or explain its behavior, contrary to the updated spec.
Component area: Docs / CLI&UX.
Environment
Platforms verified: All platforms (documentation bug; observed on WSL2 Ubuntu 22.04.4 LTS)
nemoclaw: v0.0.49
openshell: 0.0.39
Docs: docs/reference/cli-selection-guide.md as shipped with NemoClaw v0.0.49
Steps to Reproduce
- On a machine with NemoClaw docs checked out (or via the rendered docs), open the CLI Selection Guide:
cat docs/reference/cli-selection-guide.md
- Scroll to the "Connect to the Sandbox" section.
- Observe which command is recommended for one-off in-sandbox commands and how
nemoclaw exec vs openshell sandbox exec are described.
Expected Result
nemoclaw --help:
- Lists
nemoclaw inference set --model <model> --provider <provider> in the "Reconfiguration (after onboard)" block.
- Still enumerates the Sandbox Management, Policy Presets (
policy-add etc.), and Messaging Channels groups.
docs/reference/cli-selection-guide.md:
(a) Recommends nemoclaw <name> exec as the primary command for one-off in-sandbox commands (NOT openshell sandbox exec).
(b) Explains that nemoclaw <name> exec runs as the sandbox user with HOME=/sandbox and picks up NemoClaw-provisioned configuration (agent config, inference route, policies, etc.).
(c) Describes openshell sandbox exec as the direct/raw OpenShell path to use ONLY when intentionally bypassing NemoClaw's wrappers and registry.
Actual Result
nemoclaw --help (NemoClaw v0.0.48) — meets the reconfiguration breadcrumb and group enumeration requirement:
"Reconfiguration (after onboard)" block includes:
- Check inference route: nemoclaw inference get
- Change inference model: nemoclaw inference set --model <model> --provider <provider>
Sandbox Management / Policy Presets / Messaging Channels groups are present with the expected commands (e.g., nemoclaw <name> exec, policy-add, channels list/add/remove/stop/start).
docs/reference/cli-selection-guide.md "Connect to the Sandbox" section (current content):
Connect to the Sandbox
Use nemoclaw <name> connect for an interactive NemoClaw sandbox shell. It waits for readiness, handles stale SSH host keys after gateway restarts, and prints agent-specific hints. Use openshell sandbox connect <name> only when you intentionally want the raw OpenShell connection path.
For a one-off command, use openshell sandbox exec instead of opening an interactive shell.
$ openshell sandbox exec -n my-assistant -- cat /tmp/gateway.log
The guide:
- Does NOT mention
nemoclaw <name> exec as the recommended one-off in-sandbox command.
- Does NOT state that
nemoclaw exec runs as the sandbox user (HOME=/sandbox) or that it uses NemoClaw-provisioned config.
- Presents
openshell sandbox exec as the default way to run one-off commands, rather than as a raw/escape hatch when intentionally bypassing NemoClaw.
This fails the spec that the CLI selection guide should point users to nemoclaw exec for NemoClaw workflows and reserve openshell sandbox exec for low-level, bypass-NemoClaw use.
Logs
Not captured — this is a docs-content bug; the Actual Result quotes the guide verbatim.
Description
docs/reference/cli-selection-guide.mdstill recommendsopenshell sandbox execas the primary one-off in-sandbox command and does not documentnemoclaw <name> execas the recommended path or explain its behavior, contrary to the updated spec.Component area: Docs / CLI&UX.
Environment
Steps to Reproduce
nemoclaw execvsopenshell sandbox execare described.Expected Result
nemoclaw --help:nemoclaw inference set --model <model> --provider <provider>in the "Reconfiguration (after onboard)" block.policy-addetc.), and Messaging Channels groups.docs/reference/cli-selection-guide.md:(a) Recommends
nemoclaw <name> execas the primary command for one-off in-sandbox commands (NOTopenshell sandbox exec).(b) Explains that
nemoclaw <name> execruns as the sandbox user withHOME=/sandboxand picks up NemoClaw-provisioned configuration (agent config, inference route, policies, etc.).(c) Describes
openshell sandbox execas the direct/raw OpenShell path to use ONLY when intentionally bypassing NemoClaw's wrappers and registry.Actual Result
nemoclaw --help(NemoClaw v0.0.48) — meets the reconfiguration breadcrumb and group enumeration requirement:Sandbox Management / Policy Presets / Messaging Channels groups are present with the expected commands (e.g.,
nemoclaw <name> exec,policy-add,channels list/add/remove/stop/start).docs/reference/cli-selection-guide.md"Connect to the Sandbox" section (current content):The guide:
nemoclaw <name> execas the recommended one-off in-sandbox command.nemoclaw execruns as the sandbox user (HOME=/sandbox) or that it uses NemoClaw-provisioned config.openshell sandbox execas the default way to run one-off commands, rather than as a raw/escape hatch when intentionally bypassing NemoClaw.This fails the spec that the CLI selection guide should point users to
nemoclaw execfor NemoClaw workflows and reserveopenshell sandbox execfor low-level, bypass-NemoClaw use.Logs
Not captured — this is a docs-content bug; the Actual Result quotes the guide verbatim.