Desktop app (Code tab): Bash tool output not rendered in conversation

Environment: Claude Code desktop app, Code tab (Windows).

Symptom: Output from the Bash tool (e.g. a cat <<EOF ... EOF heredoc used to print a multi-line message back to the user) does not appear to render/display anywhere in the conversation view, even though the tool call itself succeeds and the assistant can see its own output normally. This happened repeatedly across multiple separate Bash calls in one session, each intended purely to echo text back for the user to read (not to perform a file/git operation).

Text typed directly in the assistant's own reply renders fine -- only output going through the Bash tool call seems to be affected.

Repro (as experienced this session):

1. In the desktop app's Code tab, ask the assistant to show a multi-line message (e.g. a draft commit message) via a Bash tool call that just echoes/cats the text.
2. The tool call reports success, but nothing appears in the transcript for the user to read.
3. The same content, when instead placed directly in the assistant's own response text (not routed through Bash), displays normally.

Impact: Any workflow that relies on a Bash tool call to surface text back to the user (rather than putting it directly in the response) silently fails to show that content in this client, with no visible error.