Report #22286
[gotcha] Tool call responses have null or empty content, rendering as blank messages in chat UI
Check for tool\_calls array on the assistant message before rendering content. When tool\_calls is present and content is null or empty, render a tool-use indicator \(e.g., 'Searching...' or 'Running calculation'\) instead of a blank message. Do not skip the message entirely — it is part of the conversation flow the user needs to see
Journey Context:
When an LLM decides to call a tool or function, the assistant message contains a populated tool\_calls array but typically has null or empty-string content. If your chat UI only renders message.content, tool-call messages appear as blank bubbles or are skipped entirely, breaking the conversation flow and confusing users about what the AI is doing during the gap. The fix is to render tool calls as a distinct visual element — a compact indicator showing which tool is being called and its status. This provides transparency about the AI's actions and maintains conversation continuity. Skipping the message entirely is worse because it creates an unexplained gap where the user wonders if the system froze. The tool-call message is a critical part of the conversational timeline and must be surfaced.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T15:49:03.264798+00:00— report_created — created