@mrciphersmith/keryx 0.3.46 → 0.3.49
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 +26 -0
- package/dist/cli.js +11655 -5432
- package/dist/core.js +1997 -1010
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -1000,6 +1000,32 @@ compared at startup, and a weaker profile refuses to bind at all. See
|
|
|
1000
1000
|
[drive keryx remotely](docs/docs/guides/drive-keryx-remotely.md) for routes and
|
|
1001
1001
|
setup.
|
|
1002
1002
|
|
|
1003
|
+
### Remote control from Telegram (opt-in, off by default)
|
|
1004
|
+
|
|
1005
|
+
`/remote-control` in a running shell mirrors that session into its own topic of a
|
|
1006
|
+
Telegram supergroup: you send a line from your phone and it runs as if typed
|
|
1007
|
+
there, the reply and any approval question come back to the topic. Nothing
|
|
1008
|
+
happens until Telegram is connected to the machine: make a separate bot with
|
|
1009
|
+
BotFather and a supergroup with topics, then type `/channels` in any shell and
|
|
1010
|
+
choose Connect. The only thing you type is the bot token (hidden); your Telegram
|
|
1011
|
+
user id and the group id are found from a one-time pairing code and from adding
|
|
1012
|
+
the bot to the group as an admin with the manage topics right. Test sends a
|
|
1013
|
+
message to the group's General topic, Disconnect deletes the topics and erases the
|
|
1014
|
+
token. The connection is per machine, so use one bot per machine (Telegram allows
|
|
1015
|
+
one poller per token); `/remote-control` then turns individual sessions on. The
|
|
1016
|
+
files it writes, `remote/bot-token` (mode 600) and `remote/config.json`, can still
|
|
1017
|
+
be made by hand. The Telegram transport is the single poller inside `keryx serve` — shells
|
|
1018
|
+
talk to `serve` over loopback with a local shell token (new on every `serve`
|
|
1019
|
+
start, and never sent to an endpoint whose `serve` is gone), they never poll
|
|
1020
|
+
Telegram themselves, and a second `keryx serve` does not poll while the first one
|
|
1021
|
+
runs. At most 500 lines wait per topic, and turning it off tells the topic which
|
|
1022
|
+
queued lines will not run.
|
|
1023
|
+
Without a connection `serve` starts as before, with remote control off, and only
|
|
1024
|
+
offers the local `/channels` routes. This
|
|
1025
|
+
has been verified against a fake Bot API only; no run against real Telegram has
|
|
1026
|
+
been done yet. Setup and limits:
|
|
1027
|
+
[drive keryx remotely](docs/docs/guides/drive-keryx-remotely.md#remote-control-from-telegram).
|
|
1028
|
+
|
|
1003
1029
|
## CI integration
|
|
1004
1030
|
|
|
1005
1031
|
CI can publish normalized, committable artifacts that humans and agents read
|