@ai-ecoverse/wasi-slicc 1.45.0 → 1.46.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 +4 -3
- package/bin/slicc.wasm +0 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -5,8 +5,9 @@
|
|
|
5
5
|
`slicc` also runs inside seven's kernel, so that one seven's agent or user can prompt, watch and abort another seven's agent, and see and manage this seven's own tray. That build is `slicc.wasm`, slicc-cli's client commands compiled with `GOOS=wasip1 GOARCH=wasm` and `CGO_ENABLED=0`, and it ships as the npm package `@ai-ecoverse/wasi-slicc`, at slicc-cli's own version. seven's page holds the WebRTC link; slicc only reaches the page's link facade.
|
|
6
6
|
|
|
7
7
|
```
|
|
8
|
-
slicc <join-url> prompt [--steer | --reject] [--thinking] [--json] [--plain] <text>|@file|-
|
|
8
|
+
slicc <join-url> prompt [--allsettled <quiet>] [--steer | --reject] [--thinking] [--json] [--plain] <text>|@file|-
|
|
9
9
|
slicc <join-url> watch [--thinking] [--json] [--plain]
|
|
10
|
+
slicc <join-url> wait [--allsettled <quiet>] [--timeout <limit>] [--json]
|
|
10
11
|
slicc <join-url> abort
|
|
11
12
|
slicc tray [--json]
|
|
12
13
|
slicc tray url
|
|
@@ -17,7 +18,7 @@ slicc --version
|
|
|
17
18
|
slicc --help
|
|
18
19
|
```
|
|
19
20
|
|
|
20
|
-
- **Commands:** `prompt`, `watch` and `abort` with a join URL behave as in [Remote control](https://github.com/ai-ecoverse/slicc-cli#remote-control-slicc-prompt-watch-and-abort): the same flags, output, styling, `--json` events, resuming and exit codes, from the same code. The differences:
|
|
21
|
+
- **Commands:** `prompt`, `watch`, `wait` and `abort` with a join URL behave as in [Remote control](https://github.com/ai-ecoverse/slicc-cli#remote-control-slicc-prompt-watch-wait-and-abort): the same flags, output, styling, `--json` events, resuming and exit codes, from the same code. The differences:
|
|
21
22
|
- **Ctrl-C** ends slicc with 130 (the kernel's default for `SIGINT`), `watch` included, and a running prompt goes on in the other seven. `--abort-on-interrupt` isn't offered.
|
|
22
23
|
- **Exit 3** covers the facade's own refusals too. When the facade gives a message (`unlock the vault to continue`, or the other seven's refusal), slicc prints it instead of the Linked devices hint.
|
|
23
24
|
- **A terminal** is a standard stream that is a character device. Styling then follows `TERM`, `NO_COLOR` and `--plain` as usual.
|
|
@@ -30,7 +31,7 @@ slicc --help
|
|
|
30
31
|
- **`slicc tray retry`** reconnects the tray's links, as the Reconnect button does.
|
|
31
32
|
- **Not here:** choosing the exit (that's routing, not tray state), and SLICC six's `host join` and `host leave`: a seven follower runs no kernel or agent of its own, so following stays with `#follow=` and the UI's Leave.
|
|
32
33
|
- **Exit status:** 0, 1 on failure (`ENOTCONN` when the tray isn't connected, a facade that doesn't answer within 1 minute, or 5 minutes for `rotate` and `unlink`, which seven may ask you to approve), 2 for bad usage, 3 when seven refuses (`EACCES`).
|
|
33
|
-
- **Everything else** exits 2 with `slicc: <command> isn't available inside seven`: `follow`, `attach`, `open`, `browsers`, the default flow, `update`, `install`, and `prompt`, `watch` or `abort` without a join URL. `--help` lists only what works there.
|
|
34
|
+
- **Everything else** exits 2 with `slicc: <command> isn't available inside seven`: `follow`, `attach`, `open`, `browsers`, the default flow, `update`, `install`, and `prompt`, `watch`, `wait` or `abort` without a join URL. `--help` lists only what works there.
|
|
34
35
|
- **What the build leaves out** (build constraints): pion and the link, CDP, SSH, mounts, the kernel listener, the policy, browser discovery, telemetry and updates.
|
|
35
36
|
|
|
36
37
|
**The link facade.** slicc reads its address from `SLICC_LINK_URL` only, as `tcp://127.0.0.1:<port>` on the kernel's loopback (any `127.x` address, or `localhost`). Without it, or with another shape, slicc exits 1. Each `agent` stream (see [`agent`](https://github.com/ai-ecoverse/slicc-cli#agent-page-cap-agent-node--page)) is one connection, carrying records of a `u8` type, a `u32` big-endian length and the payload, both ways:
|
package/bin/slicc.wasm
CHANGED
|
Binary file
|
package/package.json
CHANGED