@okxweb3/a2a-node 0.0.16 → 0.0.17-beta-db5dca184d-260624144716
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 +40 -6
- package/dist/cli.js +584 -292
- package/dist/index.js +29 -12
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -23,9 +23,13 @@ npm -w @okxweb3/a2a-node test
|
|
|
23
23
|
|
|
24
24
|
```bash
|
|
25
25
|
okx-a2a daemon start --provider codex
|
|
26
|
+
okx-a2a daemon start --provider codex --no-autostart
|
|
26
27
|
okx-a2a daemon restart --provider claude
|
|
27
28
|
okx-a2a daemon status
|
|
28
29
|
okx-a2a daemon stop
|
|
30
|
+
okx-a2a daemon autostart install
|
|
31
|
+
okx-a2a daemon autostart status
|
|
32
|
+
okx-a2a daemon autostart uninstall
|
|
29
33
|
|
|
30
34
|
# Legacy aliases are still supported:
|
|
31
35
|
okx-a2a start
|
|
@@ -35,12 +39,42 @@ okx-a2a stop
|
|
|
35
39
|
okx-a2a run
|
|
36
40
|
```
|
|
37
41
|
|
|
38
|
-
`daemon start` records the default AI provider in the local SQLite store
|
|
39
|
-
only one of `codex` or `claude` is
|
|
40
|
-
both are installed, the CLI asks in
|
|
41
|
-
mode pass `--provider codex` or
|
|
42
|
-
accept the same provider options;
|
|
43
|
-
legacy `--ai-provider` when both are
|
|
42
|
+
`daemon start` records the default AI provider in the local SQLite store and
|
|
43
|
+
installs OS autostart by default. If only one of `codex` or `claude` is
|
|
44
|
+
installed, it is selected automatically. If both are installed, the CLI asks in
|
|
45
|
+
an interactive terminal; in non-interactive mode pass `--provider codex` or
|
|
46
|
+
`--provider claude`. `start` and `restart` accept the same provider options;
|
|
47
|
+
`--provider` takes precedence over the legacy `--ai-provider` when both are
|
|
48
|
+
present. Pass `--no-autostart` to start only the current daemon process without
|
|
49
|
+
installing boot/login autostart.
|
|
50
|
+
|
|
51
|
+
## Autostart
|
|
52
|
+
|
|
53
|
+
Linux autostart is managed as a user-level systemd service. macOS autostart is
|
|
54
|
+
managed as a LaunchAgent. Both are installed by `daemon start` unless
|
|
55
|
+
`--no-autostart` is set, and can also be managed explicitly:
|
|
56
|
+
|
|
57
|
+
```bash
|
|
58
|
+
okx-a2a daemon autostart install
|
|
59
|
+
okx-a2a daemon autostart status
|
|
60
|
+
okx-a2a daemon autostart uninstall
|
|
61
|
+
```
|
|
62
|
+
|
|
63
|
+
The generated systemd service or LaunchAgent runs `okx-a2a run` in the
|
|
64
|
+
foreground so the OS supervisor can watch the actual daemon process and restart
|
|
65
|
+
it. It deliberately does not call `okx-a2a daemon start`, because
|
|
66
|
+
`daemon start` may fork a detached child and exit when `--no-autostart` is used.
|
|
67
|
+
`okx-a2a daemon autostart status` prints the autostart definition for the
|
|
68
|
+
current OS.
|
|
69
|
+
|
|
70
|
+
If the service should start before the user logs in, enable lingering separately:
|
|
71
|
+
|
|
72
|
+
```bash
|
|
73
|
+
loginctl enable-linger "$USER"
|
|
74
|
+
```
|
|
75
|
+
|
|
76
|
+
macOS does not use systemd; `okx-a2a daemon autostart install` writes a
|
|
77
|
+
LaunchAgent under `~/Library/LaunchAgents`.
|
|
44
78
|
|
|
45
79
|
Reconfigure the default provider:
|
|
46
80
|
|