Name and order the agent and config code

[onechat] / README.rst

diff --git a/README.rst b/README.rst
index 4bda34e7a09b06332c4726c6f047f31d7ce16cd4..c9aaaeeb4e1b59fa0e4ac307118508f7d7c4010f 100644 (file)
--- a/README.rst
+++ b/README.rst
@@ -131,11 +131,14 @@ new messages, so it needs no open port.
 
 The bot reads only the private chat of the owner and ignores all other
 updates. Each text message goes to the agent as a user message, and the
 
 The bot reads only the private chat of the owner and ignores all other
 updates. Each text message goes to the agent as a user message, and the

-line ``/stop`` interrupts the running turn. The bot sends the replies as
-plain text, in parts of at most 4096 characters, and each error as a
-short message. It shows the typing action while a turn runs. It does not
-send the tool calls. It sends each message that the user types in the
-terminal client, with the mark ``[terminal]``.
+line ``/stop`` interrupts the running turn. The bot sends the replies in
+parts of at most 4096 characters, with their Markdown as Telegram
+formats: bold, italic, strikethrough, code, code blocks, links, and
+headings as bold text. When Telegram refuses the formats of a part, the
+bot sends the part again as plain text. Each error goes as a short
+message in plain text. It shows the typing action while a turn runs. It
+does not send the tool calls. It sends each message that the user types
+in the terminal client, with the mark ``[terminal]``.

 
 ``agent/telegram-offset.json`` holds the ID of the next update. The bot
 moves it past an update only after the message is durable in the log, so
 
 ``agent/telegram-offset.json`` holds the ID of the next update. The bot
 moves it past an update only after the message is durable in the log, so