-
|
OpenACP says it streams tool calls, file edits, and agent thinking in real time — how does this look in Telegram specifically? Does it edit a single message as new tokens arrive or does it send multiple messages? Asking because some streaming implementations spam the chat with dozens of short messages and it gets annoying fast. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
It edits a single message in place as tokens arrive — no spam. Telegram's edit API limits updates to once per second, so OpenACP batches tokens into 1-second chunks and updates the same message. Tool calls (file reads, shell commands) appear as separate collapsed messages so you can expand them independently. The result is clean: one message per agent response, one message per tool call. |
Beta Was this translation helpful? Give feedback.
It edits a single message in place as tokens arrive — no spam. Telegram's edit API limits updates to once per second, so OpenACP batches tokens into 1-second chunks and updates the same message. Tool calls (file reads, shell commands) appear as separate collapsed messages so you can expand them independently. The result is clean: one message per agent response, one message per tool call.