@mrciphersmith/keryx 0.3.56 → 0.3.57
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 +7 -1
- package/dist/cli.js +1597 -87
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -1019,7 +1019,13 @@ talk to `serve` over loopback with a local shell token (new on every `serve`
|
|
|
1019
1019
|
start, and never sent to an endpoint whose `serve` is gone), they never poll
|
|
1020
1020
|
Telegram themselves, and a second `keryx serve` does not poll while the first one
|
|
1021
1021
|
runs. At most 500 lines wait per topic, and turning it off tells the topic which
|
|
1022
|
-
queued lines will not run.
|
|
1022
|
+
queued lines will not run. From the topic you can also run a fixed list of slash
|
|
1023
|
+
commands (`/status`, `/model` and `/connect` as buttons, `/new`, `/clear`, `/resume`
|
|
1024
|
+
in the same topic); `/mode trust`, `/plan off`, `/delegate` and `/external*` run only
|
|
1025
|
+
after a Yes press, and commands such as `/mcp`, `/guard`, `/route`, `/provider`,
|
|
1026
|
+
`/schedule`, `/rewind`, `/conform` and `/ci` stay local. Each message shows its state as a reaction and the topic shows typing
|
|
1027
|
+
while a turn runs; see
|
|
1028
|
+
[commands from the topic](docs/docs/guides/drive-keryx-remotely.md#commands-from-the-topic).
|
|
1023
1029
|
Without a connection `serve` starts as before, with remote control off, and only
|
|
1024
1030
|
offers the local `/channels` routes. This
|
|
1025
1031
|
has been verified against a fake Bot API only; no run against real Telegram has
|