Skip to content

Commit 20d0c95

Browse files
authored
fix: remove openclaw nemoclaw CLI commands, keep provider and slash command (#492)
* 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
1 parent 5b9d557 commit 20d0c95

28 files changed

Lines changed: 82 additions & 2572 deletions

‎README.md‎

Lines changed: 1 addition & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -219,21 +219,7 @@ Run these on the host to set up, connect to, and manage sandboxes.
219219
| `openshell term` | Launch the OpenShell TUI for monitoring and approvals. |
220220
| `nemoclaw start` / `stop` / `status` | Manage auxiliary services (Telegram bridge, tunnel). |
221221

222-
### Plugin commands (`openclaw nemoclaw`)
223-
224-
Run these inside the OpenClaw CLI. These commands are under active development and may not all be functional yet.
225-
226-
| Command | Description |
227-
|--------------------------------------------|----------------------------------------------------------|
228-
| `openclaw nemoclaw launch [--profile ...]` | Bootstrap OpenClaw inside an OpenShell sandbox. |
229-
| `openclaw nemoclaw status` | Show sandbox health, blueprint state, and inference. |
230-
| `openclaw nemoclaw logs [-f]` | Stream blueprint execution and sandbox logs. |
231-
232-
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.
237223

238224
---
239225

‎docs/about/how-it-works.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,7 @@ Thin plugin, versioned blueprint
7575
: The plugin stays small and stable. Orchestration logic lives in the blueprint and evolves on its own release cadence.
7676

7777
Respect CLI boundaries
78-
: The `nemoclaw` CLI is the primary interface. Plugin commands are available under `openclaw nemoclaw` but do not override built-in OpenClaw commands.
78+
: The `nemoclaw` CLI is the primary interface for sandbox management.
7979

8080
Supply chain safety
8181
: Blueprint artifacts are immutable, versioned, and digest-verified before execution.
@@ -91,7 +91,7 @@ Reproducible setup
9191

9292
NemoClaw is split into two parts:
9393

94-
- The *plugin* is a TypeScript package that powers the `nemoclaw` CLI and also registers commands under `openclaw nemoclaw`.
94+
- The *plugin* is a TypeScript package that registers an inference provider and the `/nemoclaw` slash command inside the sandbox.
9595
It handles user interaction and delegates orchestration work to the blueprint.
9696
- The *blueprint* is a versioned Python artifact that contains all the logic for creating sandboxes, applying policies, and configuring inference.
9797
The plugin resolves, verifies, and executes the blueprint as a subprocess.

‎docs/inference/switch-inference-providers.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -44,13 +44,13 @@ The `nemoclaw onboard` command stores this key in `~/.nemoclaw/credentials.json`
4444
Run the status command to confirm the change:
4545

4646
```console
47-
$ openclaw nemoclaw status
47+
$ nemoclaw <name> status
4848
```
4949

5050
Add the `--json` flag for machine-readable output:
5151

5252
```console
53-
$ openclaw nemoclaw status --json
53+
$ nemoclaw <name> status --json
5454
```
5555

5656
The output includes the active provider, model, and endpoint.

‎docs/monitoring/monitor-sandbox-activity.md‎

Lines changed: 6 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -32,13 +32,7 @@ Use the NemoClaw status, logs, and TUI tools together to inspect sandbox health,
3232
Run the status command to view the sandbox state, blueprint run information, and active inference configuration:
3333

3434
```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
4236
```
4337

4438
Key fields in the output include the following:
@@ -47,33 +41,22 @@ Key fields in the output include the following:
4741
- Blueprint run ID, which is the identifier for the most recent blueprint execution.
4842
- Inference provider, which shows the active provider, model, and endpoint.
4943

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.
5145

5246
## View Blueprint and Sandbox Logs
5347

5448
Stream the most recent log output from the blueprint runner and sandbox:
5549

5650
```console
57-
$ openclaw nemoclaw logs
51+
$ nemoclaw <name> logs
5852
```
5953

6054
To follow the log output in real time:
6155

6256
```console
63-
$ openclaw nemoclaw logs -f
57+
$ nemoclaw <name> logs -f
6458
```
6559

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:
73-
74-
```console
75-
$ openclaw nemoclaw logs --run-id <id>
76-
```
7760

7861
## Monitor Network Activity in the TUI
7962

@@ -104,8 +87,8 @@ $ openclaw agent --agent main --local -m "Test inference" --session-id debug
10487

10588
If the request fails, check the following:
10689

107-
1. Run `openclaw nemoclaw status` to confirm the active provider and endpoint.
108-
2. Run `openclaw nemoclaw logs -f` to view error messages from the blueprint runner.
90+
1. Run `nemoclaw <name> status` to confirm the active provider and endpoint.
91+
2. Run `nemoclaw <name> logs -f` to view error messages from the blueprint runner.
10992
3. Verify that the inference endpoint is reachable from the host.
11093

11194
## Related Topics

‎docs/network-policy/customize-network-policy.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ The wizard picks up the modified policy file and applies it to the sandbox.
6262
Check that the sandbox is running with the updated policy:
6363

6464
```console
65-
$ openclaw nemoclaw status
65+
$ nemoclaw <name> status
6666
```
6767

6868
## Dynamic Changes

‎docs/reference/architecture.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,8 +24,8 @@ NemoClaw has two main components: a TypeScript plugin that integrates with the O
2424

2525
## NemoClaw Plugin
2626

27-
The plugin is a thin TypeScript package that registers commands under `openclaw nemoclaw`.
28-
It runs in-process with the OpenClaw gateway and handles user-facing CLI interactions.
27+
The plugin is a thin TypeScript package that registers an inference provider and the `/nemoclaw` slash command.
28+
It runs in-process with the OpenClaw gateway inside the sandbox.
2929

3030
```text
3131
nemoclaw/

‎docs/reference/commands.md‎

Lines changed: 1 addition & 71 deletions
Original file line numberDiff line numberDiff line change
@@ -20,77 +20,7 @@ status: published
2020

2121
# Commands
2222

23-
NemoClaw provides two command interfaces.
24-
The plugin commands run under the `openclaw nemoclaw` namespace inside the OpenClaw CLI.
25-
The standalone `nemoclaw` binary handles host-side setup, deployment, and service management.
26-
Both interfaces are installed when you run `npm install -g nemoclaw`.
27-
28-
## Plugin Commands
29-
30-
### `openclaw nemoclaw launch`
31-
32-
Bootstrap OpenClaw inside an OpenShell sandbox.
33-
If NemoClaw detects an existing host installation, `launch` stops unless you pass `--force`.
34-
35-
```console
36-
$ openclaw nemoclaw launch [--force] [--profile <profile>]
37-
```
38-
39-
`--force`
40-
: 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.
77-
78-
### `openclaw nemoclaw logs`
79-
80-
Stream blueprint execution and sandbox logs.
81-
82-
```console
83-
$ openclaw nemoclaw logs [-f] [-n <count>] [--run-id <id>]
84-
```
85-
86-
`-f, --follow`
87-
: Follow log output, similar to `tail -f`.
88-
89-
`-n, --lines <count>`
90-
: Number of lines to show. Default: `50`.
91-
92-
`--run-id <id>`
93-
: Show logs for a specific blueprint run instead of the latest.
23+
The `nemoclaw` CLI is the primary interface for managing NemoClaw sandboxes. It is installed when you run `npm install -g nemoclaw`.
9424

9525
### `/nemoclaw` Slash Command
9626

‎docs/reference/troubleshooting.md‎

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -151,7 +151,7 @@ Run `nemoclaw onboard` to recreate the sandbox from the same blueprint and polic
151151
### Status shows "not running" inside the sandbox
152152

153153
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.
155155
The status command detects the sandbox context and reports "active (inside sandbox)" instead.
156156

157157
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.
162162
Check the active provider and endpoint:
163163

164164
```console
165-
$ openclaw nemoclaw status
165+
$ nemoclaw <name> status
166166
```
167167

168168
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
184184
View the error output for the failed blueprint run:
185185

186186
```console
187-
$ openclaw nemoclaw logs --run-id <id>
187+
$ nemoclaw <name> logs
188188
```
189189

190-
If the run ID is unknown, omit `--run-id` to view logs from the most recent run.
191190
Use `--follow` to stream logs in real time while debugging.

‎nemoclaw-blueprint/policies/openclaw-sandbox.yaml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@
1010
# strict — this file. Minimum for onboard + basic agent operation.
1111
# relaxed — adds third-party model providers, broader web access.
1212
#
13-
# To add endpoints: update this file and re-run `openclaw nemoclaw migrate`
13+
# To add endpoints: update this file and re-run `nemoclaw onboard`
1414
# or apply dynamically via `openshell policy set`.
1515

1616
version: 1

‎nemoclaw/src/blueprint/exec.ts‎

Lines changed: 0 additions & 98 deletions
This file was deleted.

0 commit comments

Comments
 (0)