You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 20d0c95
Browse filesBrowse the repository at this point in the historyBrowse files
* fix: remove openclaw nemoclaw CLI commands, keep provider and slash command
Fixes#487, #489. The `openclaw nemoclaw` CLI subcommands have been removed.
The NemoClaw host CLI (`nemoclaw`) is the only supported CLI interface.
The OpenClaw plugin still registers an inference provider and /nemoclaw
slash command inside the sandbox — only the CLI commands are removed.
- Delete cli.ts and 8 command files (launch, status, logs, connect, migrate, eject, onboard)
- Delete dead code (blueprint/exec, fetch, resolve, verify; onboard/prompt, validate)
- Keep slash.ts, migration-state.ts, blueprint/state.ts, onboard/config.ts
- Remove registerCli() from index.ts
- Update slash command help text to reference nemoclaw host CLI
- Remove plugin commands section from README and docs
- Update all openclaw nemoclaw references across 7 doc files
- Update e2e test assertions for removed dist files
* ci: pass vitest with no test files after removing status.test.ts
* test: add plugin registration test verifying no CLI commands registered
* docs: fix stale flag references caught by CodeRabbit review
See the full [CLI reference](https://docs.nvidia.com/nemoclaw/latest/reference/commands.html) for all commands, flags, and options.
233
-
234
-
> **Known limitations:**
235
-
> - The `openclaw nemoclaw` plugin commands are under active development. Use the `nemoclaw` host CLI as the primary interface.
236
-
> - Setup may require manual workarounds on some platforms. File an issue if you encounter blockers.
222
+
See the full [CLI reference](https://docs.nvidia.com/nemoclaw/latest/reference/commands.md) for all commands, flags, and options.
Copy file name to clipboardExpand all lines: docs/monitoring/monitor-sandbox-activity.md
+6-23Lines changed: 6 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,13 +32,7 @@ Use the NemoClaw status, logs, and TUI tools together to inspect sandbox health,
32
32
Run the status command to view the sandbox state, blueprint run information, and active inference configuration:
33
33
34
34
```console
35
-
$ openclaw nemoclaw status
36
-
```
37
-
38
-
For machine-readable output, add the `--json` flag:
39
-
40
-
```console
41
-
$ openclaw nemoclaw status --json
35
+
$ nemoclaw <name> status
42
36
```
43
37
44
38
Key fields in the output include the following:
@@ -47,33 +41,22 @@ Key fields in the output include the following:
47
41
- Blueprint run ID, which is the identifier for the most recent blueprint execution.
48
42
- Inference provider, which shows the active provider, model, and endpoint.
49
43
50
-
If you run `openclaw nemoclaw status`from inside the sandbox, the command detects the sandbox context and reports it. Host-level sandbox and inference details are not available from within the sandbox. Run `openshell sandbox list`on the host to check the underlying sandbox state.
44
+
Run `nemoclaw <name> status`on the host to check sandbox state. Use `openshell sandbox list`for the underlying sandbox details.
51
45
52
46
## View Blueprint and Sandbox Logs
53
47
54
48
Stream the most recent log output from the blueprint runner and sandbox:
55
49
56
50
```console
57
-
$ openclaw nemoclaw logs
51
+
$ nemoclaw<name> logs
58
52
```
59
53
60
54
To follow the log output in real time:
61
55
62
56
```console
63
-
$ openclaw nemoclaw logs -f
57
+
$ nemoclaw<name> logs -f
64
58
```
65
59
66
-
To display a specific number of log lines:
67
-
68
-
```console
69
-
$ openclaw nemoclaw logs -n 100
70
-
```
71
-
72
-
To view logs for a specific blueprint run instead of the most recent one:
: Skip the ergonomics warning and force plugin-driven bootstrap. Without this flag,
41
-
NemoClaw recommends using `openshell sandbox create` directly for new installs.
42
-
43
-
`--profile <profile>`
44
-
: Blueprint profile to use. Default: `default`.
45
-
46
-
### `nemoclaw <name> connect`
47
-
48
-
Open an interactive shell inside the OpenClaw sandbox.
49
-
Use this after launch to connect and chat with the agent through the TUI or CLI.
50
-
51
-
```console
52
-
$ nemoclaw my-assistant connect
53
-
```
54
-
55
-
If the TUI view is not a good fit for very long responses, use the CLI form instead:
56
-
57
-
```console
58
-
$ openclaw agent --agent main --local -m "<prompt>" --session-id <id>
59
-
```
60
-
61
-
This is the recommended workaround when you need the full response printed directly in the terminal.
62
-
63
-
### `openclaw nemoclaw status`
64
-
65
-
Display sandbox health, blueprint run state, and inference configuration.
66
-
67
-
```console
68
-
$ openclaw nemoclaw status [--json]
69
-
```
70
-
71
-
`--json`
72
-
: Output as JSON for programmatic consumption.
73
-
74
-
When running inside an active OpenShell sandbox, the status command detects the sandbox context and reports "active (inside sandbox)" instead of false negatives.
75
-
Host-side sandbox state and inference configuration are not inspectable from inside the sandbox.
76
-
Run `openshell sandbox list` on the host to check the underlying sandbox state.
Copy file name to clipboardExpand all lines: docs/reference/troubleshooting.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -151,7 +151,7 @@ Run `nemoclaw onboard` to recreate the sandbox from the same blueprint and polic
151
151
### Status shows "not running" inside the sandbox
152
152
153
153
This is expected behavior.
154
-
When running `openclaw nemoclaw status` inside an active sandbox, host-side sandbox state and inference configuration are not inspectable.
154
+
When checking status inside an active sandbox, host-side sandbox state and inference configuration are not inspectable.
155
155
The status command detects the sandbox context and reports "active (inside sandbox)" instead.
156
156
157
157
Run `openshell sandbox list` on the host to check the underlying sandbox state.
@@ -162,7 +162,7 @@ Verify that the inference provider endpoint is reachable from the host.
162
162
Check the active provider and endpoint:
163
163
164
164
```console
165
-
$ openclaw nemoclaw status
165
+
$ nemoclaw<name> status
166
166
```
167
167
168
168
If the endpoint is correct but requests still fail, check for network policy rules that may block the connection, and verify that your NVIDIA API key is valid.
@@ -184,8 +184,7 @@ Refer to [Customize the Network Policy](../network-policy/customize-network-poli
184
184
View the error output for the failed blueprint run:
185
185
186
186
```console
187
-
$ openclaw nemoclaw logs --run-id <id>
187
+
$ nemoclaw <name> logs
188
188
```
189
189
190
-
If the run ID is unknown, omit `--run-id` to view logs from the most recent run.
191
190
Use `--follow` to stream logs in real time while debugging.
0 commit comments