@native-engagement/cli 0.10.0 → 0.11.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +41 -0
- package/dist/index.js +33 -10
- package/dist/skills/native-engagement-node-installation/SKILL.md +31 -0
- package/package.json +2 -1
- package/release.json +2 -3
package/README.md
ADDED
|
@@ -0,0 +1,41 @@
|
|
|
1
|
+
# Native Engagement CLI
|
|
2
|
+
|
|
3
|
+
Command-line access to Native Engagement for people and existing Agent Runtimes. Requires Node.js 24.22.1 or later in the Node.js 24 line.
|
|
4
|
+
|
|
5
|
+
```sh
|
|
6
|
+
npm install --global @native-engagement/cli@0.11.0
|
|
7
|
+
native-engagement --help
|
|
8
|
+
native-engagement login
|
|
9
|
+
native-engagement auth status
|
|
10
|
+
```
|
|
11
|
+
|
|
12
|
+
Use the trusted HTTPS service URL supplied by your administrator. `NATIVE_ENGAGEMENT_API_URL` selects another authorized service. Account credentials and MFA are entered on the browser sign-in page. For a browser opened separately on macOS or Linux, use `native-engagement login --no-open` and follow the private local handoff file.
|
|
13
|
+
|
|
14
|
+
The CLI saves login grants in a protected current-user directory. `native-engagement logout` revokes and removes the saved grant. Existing automation hosts may supply an authorized short-lived token through their protected environment. Password and token arguments are not supported.
|
|
15
|
+
|
|
16
|
+
## Discover and call capabilities
|
|
17
|
+
|
|
18
|
+
```sh
|
|
19
|
+
native-engagement contracts list
|
|
20
|
+
native-engagement schema get execution.device.list
|
|
21
|
+
native-engagement query <contract-name> --input @request.json
|
|
22
|
+
native-engagement command <contract-name> --input @command.json
|
|
23
|
+
```
|
|
24
|
+
|
|
25
|
+
Inputs follow the current schema. Commands require a stable `idempotencyKey`. Keep original requests and receipts; inspect an unknown external outcome before retrying. Business permissions and any required Human approval apply to every operation.
|
|
26
|
+
|
|
27
|
+
Results are structured JSON. Exit codes: 0 for success, 2 for rejected input or access, 1 for an unavailable operation.
|
|
28
|
+
|
|
29
|
+
## Prepare an execution environment
|
|
30
|
+
|
|
31
|
+
```sh
|
|
32
|
+
native-engagement skill installation
|
|
33
|
+
```
|
|
34
|
+
|
|
35
|
+
This offline guide explains prerequisites and dependency reuse. The CLI is a remote client, so installing it does not register a local execution node or install another Agent Runtime. Reuse an existing authorized execution environment when available.
|
|
36
|
+
|
|
37
|
+
For a new environment, discover the environment request capabilities and follow their authenticated installation handoff. The host Agent can install trusted local execution programs and selected authorized dependencies. Reuse compatible programs and caches; preserve identity, credentials, task journals and recovery state when updating. A Desktop application is optional.
|
|
38
|
+
|
|
39
|
+
## License
|
|
40
|
+
|
|
41
|
+
Apache-2.0. Bundled third-party notices are included in `THIRD_PARTY_LICENSES.txt`.
|