Show styled replies only on terminal output

[onechat] / README.rst

diff --git a/README.rst b/README.rst
index 18af25626790ed7c2defd843f576c503b4fa3130..23462b43ecaa2167feed93a769d1ee5de5c7be84 100644 (file)
--- a/README.rst
+++ b/README.rst
@@ -83,14 +83,16 @@ listens on the Unix socket ``onechat.sock`` there. In the client, each
 line is a message to the agent, the line ``/stop`` interrupts the
 running turn, the line ``/stop NAME`` stops the subagent NAME, and
 Ctrl-D ends the client. The client shows the replies, the tool calls,
 line is a message to the agent, the line ``/stop`` interrupts the
 running turn, the line ``/stop NAME`` stops the subagent NAME, and
 Ctrl-D ends the client. The client shows the replies, the tool calls,

-and the first lines of each tool result as they happen. It also shows
-each message that the user sends from another client, with the client as
-a mark, such as ``[telegram] text``. When a subagent starts, the client
-shows ``[NAME] started``, and it shows the whole report of the subagent,
-which starts with ``[NAME]``, but not the tool calls of the subagent.
-The daemon is the only process that uses the token file while it runs,
-so ``onechat login`` and ``onechat probe`` refuse to start until it
-stops.
+and the first lines of each tool result as they happen. Replies and
+subagent reports render Markdown with styles and wrapped tables only
+when the output is a terminal, and stay unchanged in a pipe or file. It
+also shows each message that the user sends from another client, with
+the client as a mark, such as ``[telegram] text``. When a subagent
+starts, the client shows ``[NAME] started``, and it shows the whole
+report of the subagent, which starts with ``[NAME]``, but not the tool
+calls of the subagent. The daemon is the only process that uses the
+token file while it runs, so ``onechat login`` and ``onechat probe``
+refuse to start until it stops.

 
 The agent runs commands with bash as the user in its working directory,
 with no sandbox. It has the rights of the user, also on the token file.
 
 The agent runs commands with bash as the user in its working directory,
 with no sandbox. It has the rights of the user, also on the token file.