@ai-ecoverse/slicc 1.51.2 → 1.52.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 +46 -12
- package/package.json +7 -7
package/README.md
CHANGED
|
@@ -330,7 +330,7 @@ Release builds (a plain `X.Y.Z` version, linked in or, for `go install`, from th
|
|
|
330
330
|
slicc capabilities [--json]
|
|
331
331
|
```
|
|
332
332
|
|
|
333
|
-
`slicc capabilities --json` is the handshake of a program that drives `slicc`, such as a native app: one JSON document on stdout, from the binary's own tables, so it describes exactly the `slicc` it came from. It reads no files, asks no network, sends no telemetry and prints no update notice, so it works the same inside an app bundle. Without `--json` it prints the version, the contract and a table of the commands.
|
|
333
|
+
`slicc capabilities --json` is the handshake of a program that drives `slicc`, such as a native app: one JSON document on stdout, from the binary's own tables, so it describes exactly the `slicc` it came from. It runs before anything else `slicc` does at start: it reads no files (not even slicc's data folder, which other commands look at for companion tools), asks no network, sends no telemetry and prints no update notice, so it works the same inside an app bundle, with no home directory at all. Without `--json` it prints the version, the contract and a table of the commands.
|
|
334
334
|
|
|
335
335
|
```
|
|
336
336
|
{"schema":1,"version":"<slicc version>","contract":1,"commands":{"<name>":{"json":"document"|"events"|"none","vocabulary"?:"events"|"agent"}},"events":{"schema":1,"names":[…]},"agent":{"events":[…],"own":[…]},"control":{"v":1,"ops":["status",…]}}
|
|
@@ -346,6 +346,37 @@ slicc capabilities [--json]
|
|
|
346
346
|
|
|
347
347
|
A program reads `contract` and the names it needs, and treats anything it doesn't know as absent: an older `slicc` lacks the newer commands, events and ops, and a newer one may have more. `TestCapabilitiesNameEveryCommandEventAndOp` fails when a command, an event or a control op is added to the code without appearing here, and keeps the document's fixture, [`test/integration/testdata/native/capabilities.json`](test/integration/testdata/native/capabilities.json), in step with the binary.
|
|
348
348
|
|
|
349
|
+
### Lifecycle events: `--json` on `attach`, `open`, `pair` and `follow`
|
|
350
|
+
|
|
351
|
+
With `--json`, `attach`, `open`, `pair` (and `--default-browser`, which is `open`) and `follow` print the NDJSON of [the default's `--json`](#the-default-slicc) on stdout: one event a line, each with `"schema": 1` and `event`, from the same vocabulary. stdout carries nothing else: `open` and `pair` put the pairing URL in a `pairing` event instead of a line of its own. Status lines stay on stderr, and so does every error, which also comes as an `error` event. Fields marked `?` are left out when empty. New fields and events may be added, and existing ones keep their meaning. Without `--json` nothing changes.
|
|
352
|
+
|
|
353
|
+
- `connecting`: `mode`, `attempt?`. A dial or setup starts: for `attach`, the CDP connection (`mode` `cdp`), then each offer from seven; for `open` and `pair`, each offer (`loopback`); for `follow`, each dial of the tray hub (`tray`), with `attempt` from the first reconnect on, the `attempt` of the `reconnecting` before it.
|
|
354
|
+
- `pairing`: `url`, on `open` and `pair`, for the first pairing URL and each new one (Enter on stdin). It is never a join URL. The pairing URL holds a one-time token and works as a secret for 10 minutes; it is printed by design, as without `--json`.
|
|
355
|
+
- `linked`: `mode`, `peer?` (the name in seven's HELLO), `tab?` (the page's origin, for `attach`), `device?` (the page's certificate fingerprint, for `open` and `pair`), `caps`, `policy` (the summary), and `resources`, what this link offers, as seven sees it:
|
|
356
|
+
- `browsers`: `[{"id","name","role","owned"}]`, the browsers listed for `cdp` (`role` `seven` or `extra`; `owned` is `true` for a browser this run launched, so never on these commands); `[]` without `cdp`;
|
|
357
|
+
- `mounts`: `[{"name","path","readOnly"}]`, the folders shared over `fs`, with the resolved path on this machine;
|
|
358
|
+
- `rejectedMounts`: `[{"path","reason"}]`, the `--mount` folders left out, with `path` as given and `reason` `not-a-folder`, `fenced` (slicc never shares it, see [Host folders](#host-folders)), `invalid-name` or `name-taken`;
|
|
359
|
+
- `network`: `{"exit","policy"}`, whether `net` goes out from this machine, and the policy summary;
|
|
360
|
+
- `compute`: `{"ssh","sftp"}`;
|
|
361
|
+
- `jerk`: `{"offered","seal"}`, the `jerk` and `jerk-seal` caps;
|
|
362
|
+
- `kernelPort?`: the local port of [kernel services](#kernel-services), when they are on.
|
|
363
|
+
- `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`.
|
|
364
|
+
- `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).
|
|
365
|
+
- `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`).
|
|
366
|
+
- `closed`: `browsers: []`, the last event of every run, also one that failed or was interrupted.
|
|
367
|
+
|
|
368
|
+
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 `<…>`.
|
|
369
|
+
|
|
370
|
+
```
|
|
371
|
+
{"schema":1,"event":"connecting","mode":"tray"}
|
|
372
|
+
{"schema":1,"event":"linked","mode":"tray","peer":"seven","caps":["net","http","credentialed","ws","udp","fs","join"],"policy":"every public address","resources":{"browsers":[],"mounts":[{"name":"proj","path":"/Users/me/proj","readOnly":true}],"rejectedMounts":[],"network":{"exit":true,"policy":"every public address"},"compute":{"ssh":false,"sftp":false},"jerk":{"offered":false,"seal":false}}}
|
|
373
|
+
{"schema":1,"event":"link-lost","mode":"tray"}
|
|
374
|
+
{"schema":1,"event":"reconnecting","attempt":1,"retryAt":"2026-05-02T10:00:01Z","wait":1043}
|
|
375
|
+
{"schema":1,"event":"connecting","mode":"tray","attempt":1}
|
|
376
|
+
{"schema":1,"event":"error","message":"seven's tray has expired; get a new join URL from seven","code":"TRAY_EXPIRED","retryable":false}
|
|
377
|
+
{"schema":1,"event":"closed","browsers":[]}
|
|
378
|
+
```
|
|
379
|
+
|
|
349
380
|
## The default: `slicc`
|
|
350
381
|
|
|
351
382
|
```
|
|
@@ -364,6 +395,7 @@ slicc [--browser <id>]... [--cdp <url>]... [--page <url>] [--origin <origin>]...
|
|
|
364
395
|
- **`--json` events** in this mode, with the shapes of the other modes plus `mode: "loopback"` and `device` (the page's certificate fingerprint):
|
|
365
396
|
- `linked`: `peer?`, `caps` and `policy`, for each link that comes up;
|
|
366
397
|
- `link-lost`: `reason?` or `message?`, for each one that goes;
|
|
398
|
+
- `error` with `message` and `retryable: false` when the loopback setup fails (no free port, say), then `closed`;
|
|
367
399
|
- `closed`, with `browsers: []`, last, when slicc exits.
|
|
368
400
|
- **Then** it serves loopback links with this run's `--page`, `--origin`, `--name`, `--allow`, `--deny`, `--expose-debug-port`, `--kernel-port`, `--no-kernel`, `--no-jerk`, `--mount` and compute flags, until `SIGINT` or `SIGTERM`.
|
|
369
401
|
|
|
@@ -536,24 +568,24 @@ Launches a browser with CDP and keeps running until interrupted (Ctrl-C, `SIGINT
|
|
|
536
568
|
- Before each launch, the seven prefs are merged into the profile's `Default/Preferences`, which is created if missing: `tab_freezing_enabled: false`, `performance_tuning.tab_freezing.enabled: false`, Memory Saver off (`performance_tuning.high_efficiency_mode.state: 0`), and `[*.]sliccy.ai` plus each extra allowed origin's host as tab-discard exceptions. The exceptions go into the list `performance_tuning.tab_discarding.exceptions` (six's form) and into the map `performance_tuning.tab_discarding.exceptions_with_time`, which Chrome 154 reads and shows under "Always keep these sites active". Existing keys, exceptions and timestamps are kept, and a file that already has everything isn't rewritten. A Preferences file that isn't a JSON object is left alone. `--no-seven-flags` skips these prefs too.
|
|
537
569
|
- Chromium flags: `--remote-debugging-port=0 --user-data-dir=<profile> --no-first-run --no-default-browser-check`, the throwaway flags for a throwaway profile, the seven flags below, `--headless=new` with `--headless`, then `--url`.
|
|
538
570
|
- A throwaway profile is one inside the system temp dir (Go's `os.TempDir()`: `TMPDIR` on macOS and Linux, `TMP` or `TEMP` on Windows; symlinks resolved, case ignored on macOS and Windows). It gets `--use-mock-keychain --password-store=basic` (`browser.ThrowawaySwitches`), so Chrome never asks for the macOS keychain or a Linux password store; without a default keychain, as under a temporary `HOME`, macOS would show "Keychain Not Found". Every other profile, SLICC's and six's included, headless or not, keeps the real keychain, so its saved cookies and passwords stay readable. `browser.Throwaway(dir)` tells which is which.
|
|
539
|
-
- The seven flags keep a seven tab's kernel running while the tab is in the background: `--disable-background-timer-throttling`, `--disable-backgrounding-occluded-windows`, `--disable-renderer-backgrounding`, `--disable-background-tracing`, and `--disable-features=LocalNetworkAccessChecks,LocalNetworkAccessChecksWebSockets,IntensiveWakeUpThrottling,HighEfficiencyModeAvailable,InfiniteTabsFreezing,InfiniteTabsFreezingOnMemoryPressure,CPUMeasurementInFreezingPolicy,MemoryMeasurementInFreezingPolicy,AllowDevtoolsConnectedDiscard`. Chromium ignores feature names it doesn't know. Every Chromium browser slicc launches, with or without the seven flags, also gets `--enable-features=ForceForegroundPriorityForAllTabs`, merged with any other `--enable-features` into one switch since Chromium keeps only the last, so a loaded Mac doesn't move a hidden tab's renderer into the background priority band, where the guard can't hear from it within 30 s and refuses the tab. `--no-seven-flags` (`LaunchOptions.NoSevenFlags`) leaves them all out, along with the seven prefs above, but not `--enable-features=ForceForegroundPriorityForAllTabs`, because the guard watches every browser slicc launches, not only seven's. Chromium keeps only one `--disable-features` value, so every `--disable-features` from the seven flags and from `LaunchOptions.ExtraArgs` is merged into one switch, in order and without duplicates. The CDP port is read from the profile's `DevToolsActivePort` once `/json/version` answers with the same websocket path. slicc waits for that as long as the browser it started is running, up to 2 min, since a first start from a cold or slow disk can take well over 30 s. Every 10 s of the wait it says so: `slicc: Google Chrome is still starting (slow disk?), 10 s so far` on stderr, or the `browser-slow` event with `--json`. A browser that exits first fails the launch at once, with its exit code and the end of its output (`Google Chrome exited with code 21 after 0.4s, before writing DevToolsActivePort; its output: …`). One still running after 2 min is stopped, and the launch fails with `… is still running after 2m0s but has not written <profile>/DevToolsActivePort`. Ctrl-C, `SIGINT` or `SIGTERM` during the wait stops the browser at once, and `slicc launch` says `slicc: interrupted while <name> was starting; closed it` (`{"event":"closed"}` with `--json`) and exits 0. A browser that `open` started on macOS isn't a child of slicc, so a launch that fails or is interrupted also stops the processes that hold the profile: the `SingletonLock` owner and every process started with its `--user-data-dir`. For an Electron app, which has no SLICC profile, it stops the process running the app's executable; the launch refuses an app that is already running, so that process is the one slicc started. One that is still running 15 s later is named in the error (`… is still running as process [<pid>]`), and `slicc launch` exits 1 instead of reporting `closed`. Electron apps get the same wait for their CDP port. On macOS a browser with a window starts through `open -n -W -a <app> --args …`, so camera and microphone permissions belong to the browser, not the terminal; `--headless` runs the executable directly. A flatpak starts with `flatpak run --filesystem=<profile> <id>`.
|
|
571
|
+
- The seven flags keep a seven tab's kernel running while the tab is in the background: `--disable-background-timer-throttling`, `--disable-backgrounding-occluded-windows`, `--disable-renderer-backgrounding`, `--disable-background-tracing`, and `--disable-features=LocalNetworkAccessChecks,LocalNetworkAccessChecksWebSockets,IntensiveWakeUpThrottling,HighEfficiencyModeAvailable,InfiniteTabsFreezing,InfiniteTabsFreezingOnMemoryPressure,CPUMeasurementInFreezingPolicy,MemoryMeasurementInFreezingPolicy,AllowDevtoolsConnectedDiscard`. Chromium ignores feature names it doesn't know. Every Chromium browser slicc launches, with or without the seven flags, also gets `--enable-features=ForceForegroundPriorityForAllTabs`, merged with any other `--enable-features` into one switch since Chromium keeps only the last, so a loaded Mac doesn't move a hidden tab's renderer into the background priority band, where the guard can't hear from it within 30 s and refuses the tab. `--no-seven-flags` (`LaunchOptions.NoSevenFlags`) leaves them all out, along with the seven prefs above, but not `--enable-features=ForceForegroundPriorityForAllTabs`, because the guard watches every browser slicc launches, not only seven's. Chromium keeps only one `--disable-features` value, so every `--disable-features` from the seven flags and from `LaunchOptions.ExtraArgs` is merged into one switch, in order and without duplicates. The CDP port is read from the profile's `DevToolsActivePort` once `/json/version` answers with the same websocket path. slicc waits for that as long as the browser it started is running, up to 2 min, since a first start from a cold or slow disk can take well over 30 s. Every 10 s of the wait it says so: `slicc: Google Chrome is still starting (slow disk?), 10 s so far` on stderr, or the `browser-slow` event with `--json`. A browser that exits first fails the launch at once, with its exit code and the end of its output (`Google Chrome exited with code 21 after 0.4s, before writing DevToolsActivePort; its output: …`). One still running after 2 min is stopped, and the launch fails with `… is still running after 2m0s but has not written <profile>/DevToolsActivePort`. Ctrl-C, `SIGINT` or `SIGTERM` during the wait stops the browser at once, and `slicc launch` says `slicc: interrupted while <name> was starting; closed it` (`{"schema":1,"event":"closed"}` with `--json`) and exits 0. A browser that `open` started on macOS isn't a child of slicc, so a launch that fails or is interrupted also stops the processes that hold the profile: the `SingletonLock` owner and every process started with its `--user-data-dir`. For an Electron app, which has no SLICC profile, it stops the process running the app's executable; the launch refuses an app that is already running, so that process is the one slicc started. One that is still running 15 s later is named in the error (`… is still running as process [<pid>]`), and `slicc launch` exits 1 instead of reporting `closed`. Electron apps get the same wait for their CDP port. On macOS a browser with a window starts through `open -n -W -a <app> --args …`, so camera and microphone permissions belong to the browser, not the terminal; `--headless` runs the executable directly. A flatpak starts with `flatpak run --filesystem=<profile> <id>`.
|
|
540
572
|
- Electron apps keep their own data and get `--remote-debugging-port=<port>`, the first free port from 9333 up, so they never take 9222–9229. An app that is already running is refused, since a second instance would hand off to it; quit it first. Apps with `debugSupport: "disabled"` are refused.
|
|
541
573
|
- Shutdown: `Browser.close` over CDP; if the browser is still running 5 s later, a signal (`SIGTERM` to the browser's process group and main process; `taskkill /T` on Windows), then after 3 s a kill (`SIGKILL`; `taskkill /F /T`). The browser runs in its own process group (`CREATE_NEW_PROCESS_GROUP` on Windows), so a terminal Ctrl-C reaches only `slicc`.
|
|
542
574
|
|
|
543
|
-
Plain output: the CDP HTTP URL on stdout, status lines on stderr. With `--json`, NDJSON events on stdout:
|
|
544
|
-
- `{"event":"launched","id","name","version","engine","pid","profile","profileDir","cdp","webSocketDebuggerUrl"}` (`version`, `profile` and `profileDir` are left out when empty);
|
|
545
|
-
- `{"event":"browser-slow","id","name","elapsed"}` every 10 s while the browser is still starting (`elapsed` in seconds, see above);
|
|
546
|
-
- `{"event":"closed"}` after `slicc launch` closed the browser;
|
|
547
|
-
- `{"event":"exited"}` when the browser exited by itself;
|
|
548
|
-
- with `--profile six`, when six's Chrome was already running: `{"event":"attached","id","name","version","engine","profile","profileDir","cdp","webSocketDebuggerUrl"}` instead of `launched`, then `{"event":"detached"}` on Ctrl-C (six's Chrome keeps running) or `exited` when it quits;
|
|
549
|
-
- `{"event":"error","message"}`, then exit 1.
|
|
575
|
+
Plain output: the CDP HTTP URL on stdout, status lines on stderr. With `--json`, NDJSON events on stdout, each with `"schema": 1` and `event`, as in [the default's `--json`](#the-default-slicc) (earlier releases left `schema` out):
|
|
576
|
+
- `{"schema":1,"event":"launched","id","name","version","engine","pid","profile","profileDir","cdp","webSocketDebuggerUrl"}` (`version`, `profile` and `profileDir` are left out when empty);
|
|
577
|
+
- `{"schema":1,"event":"browser-slow","id","name","elapsed"}` every 10 s while the browser is still starting (`elapsed` in seconds, see above);
|
|
578
|
+
- `{"schema":1,"event":"closed"}` after `slicc launch` closed the browser;
|
|
579
|
+
- `{"schema":1,"event":"exited"}` when the browser exited by itself;
|
|
580
|
+
- with `--profile six`, when six's Chrome was already running: `{"schema":1,"event":"attached","id","name","version","engine","profile","profileDir","cdp","webSocketDebuggerUrl"}` instead of `launched`, then `{"schema":1,"event":"detached"}` on Ctrl-C (six's Chrome keeps running) or `exited` when it quits;
|
|
581
|
+
- `{"schema":1,"event":"error","message"}`, then exit 1.
|
|
550
582
|
|
|
551
583
|
## Local setup: `slicc attach`
|
|
552
584
|
|
|
553
585
|
```
|
|
554
586
|
slicc attach --cdp <url> [--cdp-extra <url>]... [--origin <origin>]... [--signal cdp|stdio] [--name <name>] [--allow <rule>]... [--deny <rule>]... [--expose-debug-port <port>]...
|
|
555
587
|
[--runner <argv…> [--]] [--shell <argv…> [--]] [--eval <argv…> [--]] [--eval-quiet <dur>] [--sftp | --no-sftp] [--kernel-port <n>] [--no-kernel]
|
|
556
|
-
[--mount <path>[:<name>][:ro]]...
|
|
588
|
+
[--mount <path>[:<name>][:ro]]... [--json]
|
|
557
589
|
```
|
|
558
590
|
|
|
559
591
|
`attach` links a seven that is open in a running CDP browser and serves the link until it is interrupted (`SIGINT`, `SIGTERM`), or until stdin closes with `--signal stdio`. Status lines go to stderr, and `SLICC_DEBUG=1` adds diagnostics, pion's included. pion never writes to stderr itself.
|
|
@@ -574,6 +606,7 @@ slicc attach --cdp <url> [--cdp-extra <url>]... [--origin <origin>]... [--signal
|
|
|
574
606
|
- `--kernel-port`: the local port for [kernel services](#kernel-services) (1–65535, default `80`; with `80`, a spare port in 17180–17189 when `80` can't be bound).
|
|
575
607
|
- `--no-kernel`: no kernel services; nothing listens.
|
|
576
608
|
- `--no-jerk`: don't offer this machine's slicc-jerk (caps `jerk` and `jerk-seal`, see [`jerk`](#jerk-slicc-jerk-over-the-link)).
|
|
609
|
+
- `--json`: NDJSON lifecycle events on stdout (see [Lifecycle events](#lifecycle-events---json-on-attach-open-pair-and-follow)). Not with `--signal stdio`, whose setup messages own stdout (exit 2).
|
|
577
610
|
|
|
578
611
|
**Setup over CDP.**
|
|
579
612
|
1. slicc picks the first page tab whose URL has an allowed origin. Until there is one it says `waiting for a seven tab` and watches for new tabs. After 15 s without one it says `still no seven tab` and what to do: a browser can hide seven's own tab from debugging clients, and then this setup can't work, so link through the tray ([Remote setup](#remote-setup-slicc-join-url-follow)). `SLICC_SEVEN_QUIET` (test-only, a Go duration) replaces the 15 s. A `Target.createTarget` refused by such a browser ends plain `slicc` with the same advice.
|
|
@@ -609,7 +642,7 @@ slicc attach --cdp <url> [--cdp-extra <url>]... [--origin <origin>]... [--signal
|
|
|
609
642
|
```
|
|
610
643
|
slicc open [--page <url>] [--origin <origin>]... [--name <name>] [--allow <rule>]... [--deny <rule>]... [--expose-debug-port <port>]...
|
|
611
644
|
[--kernel-port <n>] [--no-kernel] [--no-jerk] [--mount <path>[:<name>][:ro]]...
|
|
612
|
-
[--runner <argv…> [--]] [--shell <argv…> [--]] [--eval <argv…> [--]] [--eval-quiet <dur>] [--sftp | --no-sftp]
|
|
645
|
+
[--runner <argv…> [--]] [--shell <argv…> [--]] [--eval <argv…> [--]] [--eval-quiet <dur>] [--sftp | --no-sftp] [--json]
|
|
613
646
|
slicc pair [the same flags]
|
|
614
647
|
slicc --default-browser [the same flags]
|
|
615
648
|
slicc unpair [<fingerprint> | --all]
|
|
@@ -1160,7 +1193,7 @@ A command that can't start exits 127 with the reason on stderr.
|
|
|
1160
1193
|
```
|
|
1161
1194
|
slicc <join-url> follow [--exit] [--allow <rule>]... [--deny <rule>]... [--expose-debug-port <port>]... [--name <name>] [--cdp <url>]...
|
|
1162
1195
|
[--runner <argv…> [--]] [--shell <argv…> [--]] [--eval <argv…> [--]] [--eval-quiet <dur>] [--sftp | --no-sftp]
|
|
1163
|
-
[--mount <path>[:<name>][:ro]]... [--jerk] [--jerk-seal]
|
|
1196
|
+
[--mount <path>[:<name>][:ro]]... [--jerk] [--jerk-seal] [--json]
|
|
1164
1197
|
slicc - follow [flags]
|
|
1165
1198
|
slicc @<file> follow [flags]
|
|
1166
1199
|
```
|
|
@@ -1174,6 +1207,7 @@ slicc @<file> follow [flags]
|
|
|
1174
1207
|
- `--allow`, `--deny`: policy rules on top of the remote default (see [Network policy](#network-policy)). This machine's debugging ports stay denied on every address of it, whatever `--allow` says, `--allow 127.0.0.1/32` included.
|
|
1175
1208
|
- `--expose-debug-port <port>`: let seven reach this one debugging port after all (repeatable), as for `attach`. The `--cdp` ports stay denied.
|
|
1176
1209
|
- `--name`: the link's `name` and `host` in HELLO, as for `attach`.
|
|
1210
|
+
- `--json`: NDJSON lifecycle events on stdout (see [Lifecycle events](#lifecycle-events---json-on-attach-open-pair-and-follow)). Not with `--signal-only` (exit 2).
|
|
1177
1211
|
- `--runner`, `--shell`, `--eval`, `--eval-quiet`, `--sftp`, `--no-sftp`: compute over SSH (cap `ssh`), exactly as for `attach`. `direct-tcpip` forwarding goes through the remote policy, so it reaches public addresses only unless `--allow` says otherwise. `--runner` works with or without `--exit`.
|
|
1178
1212
|
- `--cdp <url>`: let seven drive this browser over the link (repeatable, in any form `slicc browsers --cdp` takes; each must answer when `follow` starts). See [`cdp`](#cdp-browser-control), and its warning: the seven on the other machine gets full control of every browser listed. No browser is `seven: true`. Without `--cdp`, `follow` doesn't offer `cdp`, and a `cdp` OPEN is refused with `EOPNOTSUPP`. Each browser's debugging port and its own endpoint addresses are [denied](#network-policy) to `tcp`, `http`, `ws`, `udp` and `ssh` forwarding.
|
|
1179
1213
|
- `--mount <path>[:<name>][:ro]`: share this folder with the seven on the other machine (cap `fs`, repeatable); see [Host folders](#host-folders). It can read the folder, and change it unless `:ro`.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@ai-ecoverse/slicc",
|
|
3
|
-
"version": "1.
|
|
3
|
+
"version": "1.52.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.
|
|
21
|
+
"@ai-ecoverse/slicc-darwin-arm64": "1.52.0",
|
|
22
|
+
"@ai-ecoverse/slicc-darwin-amd64": "1.52.0",
|
|
23
|
+
"@ai-ecoverse/slicc-linux-arm64": "1.52.0",
|
|
24
|
+
"@ai-ecoverse/slicc-linux-amd64": "1.52.0",
|
|
25
|
+
"@ai-ecoverse/slicc-windows-arm64": "1.52.0",
|
|
26
|
+
"@ai-ecoverse/slicc-windows-amd64": "1.52.0",
|
|
27
27
|
"@ai-ecoverse/slicc-jerk": "^1.3.9"
|
|
28
28
|
}
|
|
29
29
|
}
|