Skip to content

fix(site): add padding below thinking-only assistant messages#24140

Draft
jaaydenh wants to merge 1 commit intomainfrom
fix/thinking-only-message-padding
Draft

fix(site): add padding below thinking-only assistant messages#24140
jaaydenh wants to merge 1 commit intomainfrom
fix/thinking-only-message-padding

Conversation

@jaaydenh
Copy link
Copy Markdown
Contributor

@jaaydenh jaaydenh commented Apr 8, 2026

Reasoning content populates parsed.reasoning but not parsed.markdown, so hasCopyableContent evaluates to false and the action bar is not rendered. The action bar provides ~24px of invisible layout space below each message; without it, thinking-only assistant messages sit flush against the next user bubble.

Widen the render condition to always show the action bar for assistant messages (empty when there is nothing to copy) and add min-h-6 so the div maintains height even without child buttons.

Implementation notes

Root causeConversationTimeline.tsx line 636:

(hasCopyableContent || (isUser && onEditUserMessage))

For a thinking-only assistant message parsed.markdown is "", so hasCopyableContent is false and isUser is false. The entire action bar div is omitted from the DOM, removing the ~24px spacer that normal messages get.

Fix — two changes on that same block:

  1. || !isUser so the action bar always renders for assistant messages.
  2. min-h-6 on the div so it keeps 24px height even when empty (no CopyButton).

🤖 Generated by Coder Agents

Reasoning content populates parsed.reasoning but not parsed.markdown,
so hasCopyableContent evaluates to false and the action bar is not
rendered. The action bar provides ~24px of invisible layout space
below each message; without it, thinking-only assistant messages sit
flush against the next user bubble.

Widen the render condition to always show the action bar for assistant
messages (empty when there is nothing to copy) and add min-h-6 so the
div maintains height even without child buttons.
@github-actions github-actions bot added the community Pull Requests and issues created by the community. label Apr 8, 2026
@jakehwll jakehwll removed the community Pull Requests and issues created by the community. label Apr 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants