@mrciphersmith/keryx 0.3.62 → 0.3.64
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 +10 -2
- package/dist/cli.js +1764 -394
- package/dist/core.js +15 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1044,8 +1044,16 @@ after a Yes press, and commands such as `/mcp`, `/guard`, `/route`, `/provider`,
|
|
|
1044
1044
|
while a turn runs; see
|
|
1045
1045
|
[commands from the topic](docs/docs/guides/drive-keryx-remotely.md#commands-from-the-topic).
|
|
1046
1046
|
Without a connection `serve` starts as before, with remote control off, and only
|
|
1047
|
-
offers the local `/channels` routes.
|
|
1048
|
-
|
|
1047
|
+
offers the local `/channels` routes. Replies are rendered in one of four modes,
|
|
1048
|
+
`remote.rendering` = `auto` (the default), `rich`, `html` or `plain`, set from the
|
|
1049
|
+
`/settings` row **Telegram rendering**: a table goes out as a native Telegram rich
|
|
1050
|
+
message in `auto` and `rich` (an aligned `<pre>` block in HTML), ordered and nested
|
|
1051
|
+
lists, task items and rules keep their shape, and a refused rich message falls back
|
|
1052
|
+
once to HTML and once to plain text, so a reply is never dropped. `keryx remote
|
|
1053
|
+
format-sample` prints the sample in every mode with no network, and `/channels`
|
|
1054
|
+
shows the mode and the last fallback; see
|
|
1055
|
+
[how replies look in Telegram](docs/docs/guides/drive-keryx-remotely.md#how-replies-look-in-telegram).
|
|
1056
|
+
This has been verified against a fake Bot API only; no run against real Telegram has
|
|
1049
1057
|
been done yet. Setup and limits:
|
|
1050
1058
|
[drive keryx remotely](docs/docs/guides/drive-keryx-remotely.md#remote-control-from-telegram).
|
|
1051
1059
|
|