Agent/Bot messages truncated in thread view #5787

Activity

1. hubdev4

   added

   bugSomething isn't workingSomething isn't working

   on Aug 13, 2026
2. hubdev4 commented on Aug 14, 2026

   

   hubdev4

   on Aug 14, 2026

   Author

   More actions

   Update after deeper investigation — the premise in this issue is incorrect: the relay is NOT delivering complete messages. The truncation happens before the relay, in the agent's shell execution. The Desktop UI is rendering exactly what the relay holds.

   Evidence

   We inspected the goose session DB (sessions.db) for the affected agent turns and compared the tool-call arguments with the actual relay events:

   • Tool call (goose shell tool, 2026-08-14 22:30 UTC):

     buzz messages send --channel <uuid> --reply-to <id> --content "@Iris CNPJ 34.028.316/0001-03 — consulta concluída.
     
     **Razão Social:** Empresa Brasileira de Correios e Telégrafos
     ...700+ chars of full content..." --mention <pubkey>
     

     The full multi-line content was in the command, with real newline characters inside the double-quoted --content argument.

   • Relay event (38b59203…, fetched back via CLI):

     "@Iris CNPJ 34.028.316/0001-03 — consulta concluída."
     

     — 51 chars. Cut exactly at the first newline.

   Root cause

   This is a goose issue, not a Buzz Desktop issue. On Windows, goose's shell tool executes commands via cmd /C <raw command line> (crates/goose/src/agents/platform_extensions/developer/shell.rs, build_shell_command, the "cmd" => command.arg("/C").raw_arg(command_line) branch).

   cmd.exe silently executes only the first line of any command string containing a literal newline and discards the rest — exit code 0, no stderr. Minimal repro:

   cmd.exe /d /c "echo LINEONE<LF>echo LINETWO"   → prints LINEONE only, rc=0
   

   So whenever the LLM emits a multi-line command (very common when passing multi-line strings to a CLI argument), everything after the first line is lost silently. The agent then reports success, the relay stores only line 1, and the Desktop faithfully displays line 1.

   Why "Latest Activities" showed the full text: it displays the agent's final response for the turn (which contains the complete analysis), not the channel message that was actually sent.

   Messages sent through stdin (type file.txt | buzz messages send --content -) arrive complete at the relay and render fine in the Desktop — further confirming the UI is not at fault.

   Workarounds

   1. Instruct agents to always pipe multi-line content via stdin instead of inline --content.
   2. Set GOOSE_SHELL=powershell for goose agents — validated: literal newlines inside quoted arguments survive powershell -NoProfile -NonInteractive -Command, and quoting mistakes fail loudly instead of truncating silently.

   I'll file the underlying issue against block/goose and link it here. Closing this one since it's not a Buzz bug.
3. hubdev4

   closed this as completedon Aug 14, 2026
4. hubdev4 commented on Aug 14, 2026

   

   hubdev4

   on Aug 14, 2026

   Author

   More actions

   Filed upstream: aaif-goose/goose#11259 (repo redirects from block/goose — same repository).
5. salman1993

   added a commit that references this issue on Aug 21, 2026

   test(benchmarks): expand Buzz-native dataset (#6448)

   ...

   b56a52c
6. BradGroux

   added a commit that references this issue on Aug 23, 2026

   test(benchmarks): expand Buzz-native dataset (block#6448)

   ...

   b3963c0
7. abipalli

   added a commit that references this issue on Oct 7, 2026

   test(benchmarks): expand Buzz-native dataset (block#6448)

   ...

   3b9a3fa