@ai-ecoverse/slicc 1.55.1 → 1.57.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 +103 -4
- package/package.json +8 -8
package/README.md
CHANGED
|
@@ -16,6 +16,7 @@
|
|
|
16
16
|
| `slicc launch` | launch a browser with CDP in a separate SLICC profile and print its CDP URL |
|
|
17
17
|
| `slicc <join-url> follow [--exit] [--runner …] [--cdp <url>] [--mount <path>]` | follow a seven's tray from another machine and offer its network, compute (over SSH), browsers or folders (`--exit`, `--runner`, `--cdp` and `--mount` work now; see [Remote setup](#remote-setup-slicc-join-url-follow)). `-` or `@<file>` in place of `<join-url>` reads it from stdin or a file, out of sight of `ps` |
|
|
18
18
|
| `slicc <join-url> prompt <text>`, `watch`, `wait`, `abort` | send a prompt to seven's agent and stream its answer, follow the agent as it works, wait until it has nothing left to do, or abort its run; `--cdp <url>` instead of a join URL links locally (works now; see [Remote control](#remote-control-slicc-prompt-watch-wait-and-abort)) |
|
|
19
|
+
| `slicc <join-url> agents [--watch] [--json]` | list seven's agents, the active cone and its live scoops, with their status, queue and model, once or as they change; `--cdp <url>` instead of a join URL links locally (see [Agent inventory](#agent-inventory-slicc-agents)) |
|
|
19
20
|
| `slicc <join-url> prompt`, `watch`, `wait`, `abort` inside seven | the same commands from seven's kernel, as `@ai-ecoverse/wasi-slicc` (works now; see [Inside seven](#inside-seven)) |
|
|
20
21
|
| `slicc tray [url \| rotate \| unlink <device> \| retry]` inside seven | this seven's tray: its state and devices, the join URL on request, rotate it, drop a device, reconnect (see [Inside seven](#inside-seven)) |
|
|
21
22
|
| `slicc browsers --json` | list running CDP endpoints and installed browsers, ranked |
|
|
@@ -340,7 +341,7 @@ slicc capabilities [--json]
|
|
|
340
341
|
- **`schema`:** the shape of this document, 1.
|
|
341
342
|
- **`version`:** the version `slicc --version` prints.
|
|
342
343
|
- **`contract`:** 1. It goes up only for a breaking change to a contract this document describes: a field or event that changes meaning or goes away. New commands, fields, events and ops leave it alone.
|
|
343
|
-
- **`commands`:** every command, keyed by name: `default` for `slicc` with no command, `follow`, `prompt`, `watch`, `wait` and `
|
|
344
|
+
- **`commands`:** every command, keyed by name: `default` for `slicc` with no command, `follow`, `prompt`, `watch`, `wait`, `abort` and `agents` (also after a join URL), `attach`, `open`, `pair`, `unpair`, `tray`, `browsers`, `launch`, `update`, `install`, `capabilities`, `version` and `help`. `json` says what `--json` prints: `document` (one JSON value), `events` (NDJSON, one event a line) or `none` (no `--json`). An `events` command has `vocabulary`: `events` for lines with `schema` and `event` (see [The default](#the-default-slicc) and [`slicc launch`](#slicc-launch---browser-id---profile-name---url-url---headless---no-seven-flags---json)), or `agent` for seven's agent events with `t` (see [`agent`](#agent-page-cap-agent-node--page)).
|
|
344
345
|
- **`events`:** `schema`, the `schema` every `event` line carries, and `names`, every `event` a `vocabulary: "events"` command can print, sorted.
|
|
345
346
|
- **`agent`:** `events`, the `t` of every agent event slicc knows, and `own`, the lines slicc itself adds to that stream (`settled`, `opened` and `reconnecting`, see [Remote control](#remote-control-slicc-prompt-watch-wait-and-abort)).
|
|
346
347
|
- **`control`:** `v`, the version of the [control socket](#running-links-slicc-tray) protocol, and `ops`, the ops it answers.
|
|
@@ -364,9 +365,10 @@ With `--json`, `attach`, `open`, `pair` (and `--default-browser`, which is `open
|
|
|
364
365
|
- `link-lost`: `mode`, `reason?` when slicc or seven closed the link (`slicc is exiting`, seven's `bye` reason, `unlinked by <name>` with `code` `UNLINKED` on `follow`), or `message?` for a failure; `device?` on `open` and `pair`.
|
|
365
366
|
- `reconnecting`: `attempt`, `retryAt` (RFC 3339, UTC), `wait` (milliseconds), `reason?` and `code?` (the failure that led here, and the hub's code), on `follow` before each new dial. These are the `attempt`, `retryAt` and `code` of [`slicc tray --json`](#running-links-slicc-tray).
|
|
366
367
|
- `error`: `message`, `code?` (the hub's or seven's code, on `follow`), `mode?`, and `retryable`: `true` when slicc goes on by itself (`follow` reconnects, and an offer from seven that slicc can't answer leaves the run waiting for the next one), `false` when the run ends, with exit 1 (exit 2 for a bad `--origin` on `attach`).
|
|
368
|
+
- `credential`: `op`, `provider`, `leaseId`, `expiresAt?`, `by`, `upstream?`, for each credential lease this process serves over [`jerk`](#jerk-slicc-jerk-over-the-link): `op` `seal` (`by` `seven`) once a lease has gone to seven, `unseal` (`by` `seven`) once seven's `unseal` has dropped one, and `revoked` (`by` `host`) once the control socket's `unseal` has dropped one. `upstream` is `true` when jerk revoked the token at the provider and `false` when it didn't (a token jerk only read lives on there until it expires); it is left out when jerk doesn't say, as with a slicc-jerk older than 1.4.0. Never a credential, a scope or a rule.
|
|
367
369
|
- `closed`: `browsers: []`, the last event of every run, also one that failed or was interrupted, and `kept: []` after the control socket's `detach`.
|
|
368
370
|
|
|
369
|
-
Secrets stay out: no join URL, no tray token, and no `--cdp` path, since `resources` names browsers by id and errors are redacted as on stderr. Fixtures: [`attach.ndjson`](test/integration/testdata/native/attach.ndjson), [`pair.ndjson`](test/integration/testdata/native/pair.ndjson), [`follow.ndjson`](test/integration/testdata/native/follow.ndjson) and [`follow-error.ndjson`](test/integration/testdata/native/follow-error.ndjson), with values that change from run to run shown as `<…>`.
|
|
371
|
+
Secrets stay out: no join URL, no tray token, and no `--cdp` path, since `resources` names browsers by id and errors are redacted as on stderr. Fixtures: [`attach.ndjson`](test/integration/testdata/native/attach.ndjson), [`credential.ndjson`](test/integration/testdata/native/credential.ndjson), [`pair.ndjson`](test/integration/testdata/native/pair.ndjson), [`follow.ndjson`](test/integration/testdata/native/follow.ndjson) and [`follow-error.ndjson`](test/integration/testdata/native/follow-error.ndjson), with values that change from run to run shown as `<…>`.
|
|
370
372
|
|
|
371
373
|
```
|
|
372
374
|
{"schema":1,"event":"connecting","mode":"tray"}
|
|
@@ -457,6 +459,7 @@ The cdp list follows the browsers: an extra that stops answering is taken off th
|
|
|
457
459
|
- `browser-slow`: `browser`, `name`, `role`, `elapsed` (seconds). A browser slicc launched hasn't written its `DevToolsActivePort` yet, every 10 s from 10 s on (see [`slicc launch`](#slicc-launch---browser-id---profile-name---url-url---headless---no-seven-flags---json)). The dashboard and plain mode show it as `<name> is still starting (slow disk?), <n> s so far`.
|
|
458
460
|
- `closed`: `browsers`, the ids slicc closed (always a list), and `kept` after a detach (the control socket's `detach`, or `SIGTERM` with `--keep-browsers`): the ids of the browsers this run launched and left running, with `browsers` `[]`. It is the last event of every run that got past choosing its browsers.
|
|
459
461
|
- `error`: `message`, and `browser?` when closing that browser failed. A setup error ends the run with exit 1.
|
|
462
|
+
- `credential`: `op`, `provider`, `leaseId`, `expiresAt?`, `by`, `upstream?`, as on [`attach`](#lifecycle-events---json-on-attach-open-pair-and-follow), for each credential lease this run seals, unseals or revokes over `jerk`.
|
|
460
463
|
- `mode`: `mode` (`loopback`) and `reason` (`no-browser`), when the run [falls back](#the-default-slicc) to the default browser. Then come `pairing`, `linked` and `link-lost` events (each `linked` and `link-lost` with `mode` and `device`, the page's fingerprint), and `closed` with `browsers: []`.
|
|
461
464
|
- `pairing`: `url`, a pairing URL, after `mode`.
|
|
462
465
|
|
|
@@ -832,6 +835,12 @@ Link spec §5.14 (J1). slicc-jerk (`jerk`, [Companion tools](#companion-tools))
|
|
|
832
835
|
|
|
833
836
|
A page RESET or a closed link kills the jerk it started.
|
|
834
837
|
|
|
838
|
+
**The host's say over leases.** A process that offers `jerk-seal` keeps, in memory, the leases it has sealed into seven: provider, lease id, expiry and when, never the credentials. Its [control socket](#running-links-slicc-tray) answers four more ops, and its `--json` prints a `credential` event for each seal, unseal and revoke ([Lifecycle events](#lifecycle-events---json-on-attach-open-pair-and-follow)). Fixture: [`credential.ndjson`](test/integration/testdata/native/credential.ndjson).
|
|
839
|
+
- `{ "v": 1, "op": "leases" }` → `{ "v": 1, "sealing": true, "leases": [{ "provider", "leaseId", "expiresAt", "sealedAt" }] }`, the live leases this process served. Expired ones drop out, and so does one seven unsealed.
|
|
840
|
+
- `{ "v": 1, "op": "unseal", "leaseId" }` revokes one: slicc runs the drop that seven's `unseal` runs, with no link request, and answers `{ "v": 1, "ok": true, "revoked": true, "upstream"?: true | false }` once jerk has dropped it. Then it tells seven to forget it ([§5.14](#514-jerk-caps-jerk-and-jerk-seal-page--node-j1)). A missing or malformed `leaseId` is `EPROTO`, and a lease this process didn't serve, or has already dropped, is `ENOENT`. If jerk fails, the answer is `{ "v": 1, "ok": false, "error": "EIO", "exit": <n> }` and the lease stays listed.
|
|
841
|
+
- `{ "v": 1, "op": "seal-off" }` → `{ "v": 1, "ok": true, "sealing": false }` stops issuing: every later `seal` on this process is `RESET EACCES: the host turned off sealing on this slicc`, and HELLO leaves out `jerk-seal` from the next link on. Live leases stay, and `unseal` still works. `{ "v": 1, "op": "seal-on" }` undoes it, answered with `"sealing": true`. Neither changes what the flags allow: `follow` without `--jerk-seal` has none of these ops.
|
|
842
|
+
- **After a restart:** the list lives only as long as the process, so a lease served by a `slicc` that has since exited can't be revoked through slicc. jerk's own drop still works on the host, as the same user: `FNOX_LEASE_ID=<lease id> jerk <provider> drop --lease`. Seven keeps such a lease until it expires.
|
|
843
|
+
|
|
835
844
|
**Windows:** from 1.35.0 through 1.49.34, values sent over the link could reach npm's `jerk.cmd` launcher through cmd.exe, which could expand or run them. Fixed in 1.49.35 (2026-10-30): slicc runs jerk's own `jerk.exe`, and on Windows hosts refuses `% & | ^ < > ! " ( )` and non-ASCII in values bound for jerk. Upgrade to 1.49.35 or later.
|
|
836
845
|
|
|
837
846
|
### `cdp` (browser control)
|
|
@@ -1318,6 +1327,38 @@ Otherwise, or with `--plain`, there are no escape codes:
|
|
|
1318
1327
|
|
|
1319
1328
|
Summaries are one line of at most 200 characters. Escape sequences and control characters other than newline and tab are removed from everything seven sends before it's shown.
|
|
1320
1329
|
|
|
1330
|
+
## Agent inventory: `slicc agents`
|
|
1331
|
+
|
|
1332
|
+
```
|
|
1333
|
+
slicc <join-url> agents [--watch] [--json]
|
|
1334
|
+
slicc agents --cdp <url> [--origin <origin>]... [--watch] [--json]
|
|
1335
|
+
slicc agents --signal stdio [--watch] [--json]
|
|
1336
|
+
```
|
|
1337
|
+
|
|
1338
|
+
`slicc agents` lists one seven's agents: the cone its tab shows and that cone's live scoops, each with its status, its queue and its model. It's read-only. It sends nothing to the agent, and nothing it gets carries a prompt, transcript text, a tool's name or output, an agent's name or title, a path, a URL or a credential. Agents' ids are opaque (below), so they don't carry names either.
|
|
1339
|
+
|
|
1340
|
+
- **The link:** as for `watch` (see [Remote control](#remote-control-slicc-prompt-watch-wait-and-abort)): a control-only link (`caps: []`) through the tray or over CDP, the same 1-minute wait for HELLO, and `--signal stdio` as there.
|
|
1341
|
+
- **Permission:** the `agent` cap, as for `watch`. Without it, slicc says `this seven doesn't allow remote control from this device; turn it on in seven's Linked devices` and exits 3.
|
|
1342
|
+
- **A seven that doesn't know it:** slicc says `this seven doesn't report its agents; update it` and exits 1.
|
|
1343
|
+
- **A tab without the agent** (seven still starting, or a follower tab): slicc prints seven's reason, such as `the agent is not running`, and exits 1. With `--watch` it keeps trying, as on a lost stream, and says so before each try: `slicc: <reason>; trying again` on stderr, or with `--json` `{"schema":1,"event":"error","message":"<reason>","retryable":true}` on stdout.
|
|
1344
|
+
- **Without `--watch`:** one snapshot, then exit 0.
|
|
1345
|
+
- **With `--watch`:** a new snapshot each time one comes from seven, until Ctrl-C or `SIGTERM`, then exit 0. Status lines, reconnects and their waits are those of `watch`. Every new stream starts with a whole snapshot, so nothing is resumed.
|
|
1346
|
+
- **Output:** a header line, then one row per agent, the cone first, with the first 8 characters of each id (the whole id is in `--json`), and `provider/model`, or `provider` alone when seven leaves the model out:
|
|
1347
|
+
|
|
1348
|
+
```
|
|
1349
|
+
seven on sliccy.com: 1 running, 1 waiting, 1 idle (reported 2s ago)
|
|
1350
|
+
ID KIND PARENT STATUS QUEUED MODEL SINCE
|
|
1351
|
+
hR7cZ2mV cone - waiting 0 anthropic/claude-opus-4-6 1m
|
|
1352
|
+
x3Lk9aQe scoop hR7cZ2mV running 1 anthropic/claude-sonnet-4-6 40s
|
|
1353
|
+
T7wPq0zR scoop hR7cZ2mV idle 0 azure 3m
|
|
1354
|
+
```
|
|
1355
|
+
|
|
1356
|
+
With `--watch` on a terminal the table is redrawn in place. Otherwise each snapshot is printed in full, after a blank line. Everything seven sends is stripped of escape and control characters before it's shown.
|
|
1357
|
+
- **`--json`:** one line per snapshot, `{"schema":1,"event":"inventory",…,"receivedAt"}`, with every field of seven's snapshot (see [`inventory`](#511-agent-page-cap-agent-node--page-remote-control)) and `receivedAt`, when slicc got it (RFC 3339, UTC). With `--watch`, slicc's `{"schema":1,"event":"reconnecting","attempt","retryAt","wait"}` comes before each new try, as on `follow`. Fields seven adds later are passed through. Fixture: [`agents.ndjson`](test/integration/testdata/native/agents.ndjson).
|
|
1358
|
+
- **Stale data:** seven repeats its snapshot at least every 30 s on a `--watch` stream, with a new `reportedAt`, so a snapshot whose `reportedAt` is more than a minute old is stale. `changedAt` and `seq` say when the agents last changed.
|
|
1359
|
+
- **Exit status:** `0` as above; `1` for a seven that doesn't report its agents, for a link or stream that ends before the first snapshot without `--watch`, and when the link can't be set up for good; `2` for bad usage; `3` without permission; `130` on Ctrl-C without `--watch`.
|
|
1360
|
+
- **Inside seven** it isn't available yet (`slicc: agents isn't available inside seven`).
|
|
1361
|
+
|
|
1321
1362
|
### `agent` (page cap `agent`), node → page
|
|
1322
1363
|
|
|
1323
1364
|
- **Who may:** the node opens `agent` streams only to a page whose HELLO lists `agent`, and the page refuses them with `EACCES` otherwise.
|
|
@@ -1340,6 +1381,8 @@ Summaries are one line of at most 200 characters. Escape sequences and control c
|
|
|
1340
1381
|
|
|
1341
1382
|
**`abort`:** `OPEN { "kind": "agent", "op": "abort" }`, answered OPENED `{ "aborted": true | false }` (`false` when nothing was running), then END.
|
|
1342
1383
|
|
|
1384
|
+
**`inventory`:** `OPEN { "kind": "agent", "op": "inventory", "watch"?: true }`, answered OPENED with a snapshot of the agents (§5.11). Without `watch` the page sends END next. With it, a `{"t":"inventory",…}` line with a whole new snapshot follows each change. A seven that doesn't know the op answers `EINVAL` (from before it) or `EOPNOTSUPP`, and the node treats both as unsupported.
|
|
1385
|
+
|
|
1343
1386
|
**Events,** one JSON object per line:
|
|
1344
1387
|
|
|
1345
1388
|
| event | meaning |
|
|
@@ -1399,6 +1442,7 @@ PID MODE SEVEN DEVICE STATE OFFERS
|
|
|
1399
1442
|
- `{ "v": 1, "op": "stop" }`: exactly what `SIGTERM` does. The process says `bye` to seven, closes the browsers this run launched, and exits 0; `closed.browsers` lists them with `--json`.
|
|
1400
1443
|
- `{ "v": 1, "op": "detach" }`: the process says `bye` to seven, stops the link, and leaves every browser running, the ones it launched too; with `--json`, `closed` has `browsers: []` and `kept`, the ids of the launched browsers left running (`[]` on `attach`, `open`, `pair` and `follow`, which launch none). A kept browser is found again by the next run: its `DevToolsActivePort` in its SLICC profile leads discovery to it with its seven tab open, and the next `slicc` attaches to it (`attached` with no `launched`) and links that tab.
|
|
1401
1444
|
- `{ "v": 1, "op": "revoke", "fingerprint": "<page-fp>" }`, on `open`, `pair` and the default-browser mode: close the link with that page, if any, and answer `{ "v": 1, "ok": true, "closed"?: true }` once it has. `slicc unpair` sends it (see [Linking seven in your everyday browser](#linking-seven-in-your-everyday-browser)). A missing fingerprint is `EINVAL`.
|
|
1445
|
+
- `{ "v": 1, "op": "leases" }`, `{ "v": 1, "op": "unseal", "leaseId" }`, `{ "v": 1, "op": "seal-off" }` and `{ "v": 1, "op": "seal-on" }`, on a process that offers `jerk-seal`: list, revoke and stop issuing credential leases (see [`jerk`](#jerk-slicc-jerk-over-the-link)). `unseal` answers once jerk is done, within 75 s.
|
|
1402
1446
|
- `stop` and `detach` are answered `{ "v": 1, "ok": true }` before the process acts. A process that doesn't know an op answers `{ "v": 1, "error": "EINVAL" }`, and a line that isn't a request of version 1 gets `EPROTO`.
|
|
1403
1447
|
- Signals don't change: `SIGINT` and `SIGTERM` still stop, except that `slicc --keep-browsers` makes `SIGTERM` detach.
|
|
1404
1448
|
- **Stale sockets:** liveness comes from connecting, not from the PID, so a reused PID can't fool `slicc tray`. A socket that refuses a connection is stale, and `slicc tray` removes it and says so on stderr, as `screen -wipe` does.
|
|
@@ -1684,7 +1728,7 @@ Page-opened streams are odd and node-opened streams even, never 0, and never reu
|
|
|
1684
1728
|
- **`caps`:** what this side accepts OPENs for.
|
|
1685
1729
|
- node: `net` (`tcp` and `resolve`), `http`, `ws` ([§5.15](#515-ws-cap-ws-page--node-websockets-for-kernel-programs)), `udp` ([§5.12](#512-udp-cap-udp-page--node)), `ssh`, `cdp`, `fs`, `join`, `jerk` and `jerk-seal` ([§5.14](#514-jerk-caps-jerk-and-jerk-seal-page--node-j1)).
|
|
1686
1730
|
- node, without a kind: `credentialed` ([§5.13](#513-credentialed-node-cap-http-streams-that-carry-a-value)), a promise about how the node handles `http` streams.
|
|
1687
|
-
- page: `kernel-in` ([§5.4](#54-kernel-page-cap-kernel-in-node--page)).
|
|
1731
|
+
- page: `kernel-in` ([§5.4](#54-kernel-page-cap-kernel-in-node--page)) and `jerk-revoke` ([§5.14](#514-jerk-caps-jerk-and-jerk-seal-page--node-j1)).
|
|
1688
1732
|
- **`routes`** (node only): the prefixes it offers as specific routes, plus `exit: true` when it's willing to be a default exit.
|
|
1689
1733
|
- **`policy`:** for display only; the node enforces it ([§6](#6-policy-node)).
|
|
1690
1734
|
- **`kernel`** (local node only, with kernel services): the port of the node's kernel listener ([§5.9](#59-kernel-listener-on-the-node-local-only)).
|
|
@@ -1946,6 +1990,51 @@ slicc-node's hostfs ([its README, *Host folders*](https://github.com/ai-ecoverse
|
|
|
1946
1990
|
- **Read-only status:** `busy` lines carry only the boolean and `why`. They never carry prompt text, tool arguments or output, and asking for `busy` changes nothing in the agent.
|
|
1947
1991
|
- **Ordering:** a `run start` never comes before the `busy: true` that covers it, and the `busy: false` comes after the last `run end`.
|
|
1948
1992
|
- **Computed** from the durable documents' subscriptions (the cone's and its scoops' `pi.live`, `ScoopWorkDoc.feeds` and the licks outbox), and a line goes out only when the value flips.
|
|
1993
|
+
- **`inventory`:** `OPEN { "kind": "agent", "op": "inventory", "watch"?: true }` on its own channel, for `slicc agents` and a native app that shows seven's agents. The page serves it through `remoteControl(connection).inventory()` from `@ai-ecoverse/slicc-agent/page`, which reads slicc-agent's owner-only inventory service.
|
|
1994
|
+
- **OPENED:** one snapshot:
|
|
1995
|
+
|
|
1996
|
+
```json
|
|
1997
|
+
{
|
|
1998
|
+
"v": 1,
|
|
1999
|
+
"instance": { "id": "pL4vT2nQ8sK1mX6zR0bYcA", "name": "seven on sliccy.com" },
|
|
2000
|
+
"seq": 42,
|
|
2001
|
+
"changedAt": 1767268800000,
|
|
2002
|
+
"reportedAt": 1767268802000,
|
|
2003
|
+
"counts": { "running": 1, "queued": 0, "waiting": 1, "idle": 1, "error": 0 },
|
|
2004
|
+
"agents": [
|
|
2005
|
+
{ "id": "hR7cZ2mVq9LwX4eN1sKj0A", "kind": "cone", "status": "waiting", "queued": 0, "provider": "anthropic", "model": "claude-opus-4-6", "since": 1767268740000 },
|
|
2006
|
+
{ "id": "x3Lk9aQeV2bN0cR5tY8uWg", "kind": "scoop", "parent": "hR7cZ2mVq9LwX4eN1sKj0A", "status": "running", "queued": 1, "provider": "anthropic", "model": "claude-sonnet-4-6", "since": 1767268760000 }
|
|
2007
|
+
]
|
|
2008
|
+
}
|
|
2009
|
+
```
|
|
2010
|
+
|
|
2011
|
+
- **Without `watch`,** the page sends END after OPENED.
|
|
2012
|
+
- **With `watch`,** each new snapshot follows as one DATA line, `{"t":"inventory", …}` with the same fields, until either side resets. Lines are always whole snapshots, never deltas.
|
|
2013
|
+
- A line goes out only when something other than `reportedAt` changed, at most one every 250 ms (the page's throttle), and the latest state is always sent. slicc-agent builds a snapshot from the subscriptions that feed seven's transcript and monitor, and drops one whose content didn't change. It has no timers of its own.
|
|
2014
|
+
- The page repeats the current snapshot at least every 30 s, with the same `seq` and `changedAt` and a new `reportedAt`. Its timer runs only while a `watch` stream is open.
|
|
2015
|
+
- **Fields:**
|
|
2016
|
+
- `v`: 1. A change that breaks a reader gets a new `v`.
|
|
2017
|
+
- `instance.id`: seven's own id, 22 characters of base64url from 16 random bytes, minted once per seven profile by the page and kept in its storage. A new profile, or cleared storage, gets a new id (and new agent ids). It isn't derived from anything about the user, the device or the tray. `instance.name`, when present, is the `name` of seven's HELLO.
|
|
2018
|
+
- `seq`: goes up by one with every new snapshot slicc-agent builds, within one run of seven's agent. It isn't kept: after a reload it starts again at 1. All streams of one seven see the same `seq` for the same snapshot while the agent runs. A `seq` lower than the last one seen means the agent restarted, and a client treats the stream as new.
|
|
2019
|
+
- `changedAt`: when slicc-agent built this snapshot, in ms since the epoch, from the commit that changed it. `reportedAt`: when the page sent this line.
|
|
2020
|
+
- `counts`: the number of agents in each status. They add up to the number of `agents`.
|
|
2021
|
+
- `agents`: the cone, then its live scoops in the order seven lists them.
|
|
2022
|
+
- `id`: an opaque id, 22 characters of base64url, such as `"hR7cZ2mVq9LwX4eN1sKj0A"`. The page makes it from slicc-agent's registry id with HMAC-SHA-256 under a random key it minted for this seven with `instance.id`, keeps in its storage and never sends, and takes the first 16 bytes. So it's the same for an agent across streams, reloads and restarts of that seven, and two sevens never share one. It carries nothing else: not the scoop's folder, which comes from the name the scoop was given, nor whether it's the first cone. Clients compare ids and don't read them.
|
|
2023
|
+
- `kind`: `cone` or `scoop`. `parent`, for a scoop only: the opaque `id` of the agent that started it, the cone or another scoop.
|
|
2024
|
+
- `status`, one of:
|
|
2025
|
+
- `running`: it has a run, retries and approval waits included;
|
|
2026
|
+
- `queued`: no run yet, and at least one input waits for it;
|
|
2027
|
+
- `waiting`: no run and nothing queued, but work it waits for is pending: a scoop `wait` of the cone, a feed to the scoop, or a lick for it held in the agent's outbox (the same signals as `busy`);
|
|
2028
|
+
- `error`: none of those, and its last turn ended in an error;
|
|
2029
|
+
- `idle`: none of those.
|
|
2030
|
+
- `queued`: how many inputs (prompts, follow-ups and licks) wait for it, 0 or more.
|
|
2031
|
+
- `provider` and `model`: pi's `provider` and `modelId` for the agent's conversation, such as `anthropic` and `claude-sonnet-4-6`. `provider`, one of slicc-agent's provider ids, is always sent when the agent has a model. `model` may be absent: slicc-agent sends it only when pi's model catalog has that model for that provider, so a user-named deployment (Azure), a custom inference profile or an ARN is left out. Both are left out when the agent has no model. A change of model is a new snapshot.
|
|
2032
|
+
- `since`: when the agent entered its `status`, in ms since the epoch, as slicc-agent saw it since it started.
|
|
2033
|
+
- **Scope:** the cone the tab's agent shows, the same cone `watch` and `prompt` reach, and that cone's live scoops. Never other cones, frozen cones, other kernels' agents or guest seats. When the tab selects another cone, the next snapshot is that cone's.
|
|
2034
|
+
- **Who may:** the `agent` cap, as for the other ops, and slicc-agent serves the inventory only on its owner seat. View and control seats and guests get none. Asking for it changes nothing in the agent.
|
|
2035
|
+
- **Only the tab that runs the agent answers.** Any other page, a follower tab included, answers `EOPNOTSUPP: the agent is not running`.
|
|
2036
|
+
- **Never sent,** in any field: agents' names, folders and titles (they come from chats), prompts, transcript text, tool names, arguments and output, error messages, role text, paths, URLs and base URLs, account names, endpoint registrations, anything from the vault, settings or MCP servers. The fields above are all there is, and new ones are added only under these rules.
|
|
2037
|
+
- **Older sevens:** a page from before this op answers `EINVAL` (an unknown op), and a page whose slicc-agent has no inventory answers `EOPNOTSUPP`. The node treats both as `this seven doesn't report its agents`.
|
|
1949
2038
|
- **Events:** one JSON object per line, mapped by slicc-agent from pi-durable's agent events (`watchEvents`) and handed to the page by `remoteControl(connection)` from `@ai-ecoverse/slicc-agent/page`.
|
|
1950
2039
|
- `{"t":"user","id","text","delivered"}`;
|
|
1951
2040
|
- `{"t":"text","id","delta"}`: assistant text as it streams;
|
|
@@ -2059,7 +2148,7 @@ HELLO adds `"jerk": { "version": "1.0.0" }` next to `caps`.
|
|
|
2059
2148
|
| RESET | when | in-kernel jerk exits |
|
|
2060
2149
|
|---|---|---|
|
|
2061
2150
|
| `EPROTO` | bad OPEN: unknown op, missing field, unknown param | 1 |
|
|
2062
|
-
| `EACCES` | the op isn't allowed over J1 (the table above); a remote link lacks `--jerk` or `--jerk-seal`;
|
|
2151
|
+
| `EACCES` | the op isn't allowed over J1 (the table above); a remote link lacks `--jerk` or `--jerk-seal`; `seal`/`unseal` came through the kernel facade; or a `seal` after the host's `seal-off` (`EACCES: the host turned off sealing on this slicc`) | 2 |
|
|
2063
2152
|
| `EBUSY` | a `create` is already in flight on this link (at most one at a time) | 1 |
|
|
2064
2153
|
| `ETIMEDOUT` | `create` ran past the provider `timeout` plus 30 s | 3 |
|
|
2065
2154
|
| `ECONNRESET` | host jerk died, or the link dropped | 1 |
|
|
@@ -2076,6 +2165,16 @@ HELLO adds `"jerk": { "version": "1.0.0" }` next to `caps`.
|
|
|
2076
2165
|
- list rows keep `provider`, `name`, `source`, `requires`, `cli`, `user`, `scopes`, `expires_at`, `env`, `id`, as strings, booleans or string lists.
|
|
2077
2166
|
- Everything else is dropped, including any masked token.
|
|
2078
2167
|
|
|
2168
|
+
**Host revoke and `seal-off` (node → page):** the host can revoke a lease seven holds and stop new ones, through the node's control socket ([`jerk`](#jerk-slicc-jerk-over-the-link)). Preventing future issuance and revoking what was issued are separate ops.
|
|
2169
|
+
- **The lease list:** a node that offers `jerk-seal` remembers, in memory and for as long as the process runs, each lease it sent: provider, `lease_id` and `expires_at`, never the credentials.
|
|
2170
|
+
- **Revoke:** the host's `unseal` runs `FNOX_LEASE_ID=<lease_id> jerk <provider> drop --lease --via-link` on the node, with no link request. Once jerk exits 0, the node tells seven.
|
|
2171
|
+
- **The notice:** to a page that lists the page cap `jerk-revoke`, the node sends `OPEN { "kind": "jerk-revoked", "provider": "github", "lease_id": "jerk-github-…", "by": "host" }` on the control channel. It carries no credential, scope or rule text. The page answers OPENED `{}`, then END, and the node sends END.
|
|
2172
|
+
- **Delivery:** the node sends each notice once on every link that is up and on each later link of this process whose page lists the cap, until the lease's `expires_at`. A RESET, or no answer within 10 s, is logged (`jerk: revoke notice <provider>: …`) and the notice waits for the next link. Repeats are harmless.
|
|
2173
|
+
- **No notice** after seven's own `unseal`, since seven asked.
|
|
2174
|
+
- **The page's obligation:** the page acts only on a notice from the node that created that lease. Otherwise any linked device with the cap could make seven forget another host's credential. When it seals a lease, the page keeps the per-process `node` id from the HELLO of the link the `lease` event came in on. It forgets the lease only when the HELLO `node` of the link the notice comes in on is that same id, and the `provider` and `lease_id` match. A notice from any other node, or for a `lease_id` it doesn't know, is answered OPENED `{}` and changes nothing.
|
|
2175
|
+
- **`seal-off`:** every later `seal` on that process is `RESET EACCES: the host turned off sealing on this slicc`, and HELLO leaves out `jerk-seal` from the next link on. A link already up keeps the cap in its HELLO and gets the RESET. Live leases stay, and `unseal` (seven's and the host's) still works. `seal-on` undoes it.
|
|
2176
|
+
- **A node without the list** (an older slicc, or a process that has since exited) never sends a notice. The host can still run jerk's drop itself, and seven then keeps the dead credential until it expires.
|
|
2177
|
+
|
|
2079
2178
|
**The agent-vs-user rule:**
|
|
2080
2179
|
- The caller of J1 may be the agent. So J1 only starts things a human must finish (`create`), moves tokens into a store the agent can't read (`seal`), or undoes what jerk minted (`unseal`).
|
|
2081
2180
|
- For `create`, the **sign-in page is the confirmation**. A create that would succeed without a human on a page is refused (`EACCES`).
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@ai-ecoverse/slicc",
|
|
3
|
-
"version": "1.
|
|
3
|
+
"version": "1.57.0",
|
|
4
4
|
"description": "SLICC's command line for seven: links a machine's network, compute and browsers to seven over WebRTC",
|
|
5
5
|
"license": "Apache-2.0",
|
|
6
6
|
"repository": {
|
|
@@ -18,12 +18,12 @@
|
|
|
18
18
|
"node": ">=18"
|
|
19
19
|
},
|
|
20
20
|
"optionalDependencies": {
|
|
21
|
-
"@ai-ecoverse/slicc-darwin-arm64": "1.
|
|
22
|
-
"@ai-ecoverse/slicc-darwin-amd64": "1.
|
|
23
|
-
"@ai-ecoverse/slicc-linux-arm64": "1.
|
|
24
|
-
"@ai-ecoverse/slicc-linux-amd64": "1.
|
|
25
|
-
"@ai-ecoverse/slicc-windows-arm64": "1.
|
|
26
|
-
"@ai-ecoverse/slicc-windows-amd64": "1.
|
|
27
|
-
"@ai-ecoverse/slicc-jerk": "^1.
|
|
21
|
+
"@ai-ecoverse/slicc-darwin-arm64": "1.57.0",
|
|
22
|
+
"@ai-ecoverse/slicc-darwin-amd64": "1.57.0",
|
|
23
|
+
"@ai-ecoverse/slicc-linux-arm64": "1.57.0",
|
|
24
|
+
"@ai-ecoverse/slicc-linux-amd64": "1.57.0",
|
|
25
|
+
"@ai-ecoverse/slicc-windows-arm64": "1.57.0",
|
|
26
|
+
"@ai-ecoverse/slicc-windows-amd64": "1.57.0",
|
|
27
|
+
"@ai-ecoverse/slicc-jerk": "^1.4.0"
|
|
28
28
|
}
|
|
29
29
|
}
|