Summary
The current user journey is ambiguous because NemoClaw manages OpenShell sandboxes and also ships an OpenClaw plugin, but the relationship between those layers is not clearly explained.
Problem
Users encounter multiple CLIs, overlapping commands, and different state stores without guidance on which tool they should use for which task. This causes confusion during onboarding, debugging, and normal operation.
Expected behavior
Users should understand the architecture, which commands run on the host, which commands run in the sandbox, and which workflow is recommended.
Acceptance criteria
- Add a high-level architecture page that shows the host CLI, Docker/k3s layer, sandbox, gateway, and inference router.
- Add a user-journey page that distinguishes new installs, plugin usage, and migration.
- CLI errors that come from OpenShell mention that dependency explicitly and point to the relevant docs.
- Deprecated or non-recommended workflows are clearly labeled.
Summary
The current user journey is ambiguous because NemoClaw manages OpenShell sandboxes and also ships an OpenClaw plugin, but the relationship between those layers is not clearly explained.
Problem
Users encounter multiple CLIs, overlapping commands, and different state stores without guidance on which tool they should use for which task. This causes confusion during onboarding, debugging, and normal operation.
Expected behavior
Users should understand the architecture, which commands run on the host, which commands run in the sandbox, and which workflow is recommended.
Acceptance criteria