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,
-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.
+Ctrl-D ends the client. On terminal output, the client shows ``> ``
+after each event while idle and clears it before the next event. An
+event can interrupt a line while the user types. The client shows the
+replies, the tool calls, 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.
projects / onechat / blobdiff