Agent response not visible to user despite responding correctly #8168

Open
opened 2026-02-16 18:09:19 -05:00 by yindo · 3 comments
Owner

Originally created by @kehao95 on GitHub (Jan 31, 2026).

Originally assigned to: @rekram1-node on GitHub.

Context

User initiated a casual greeting session to interact with the agent.

Problem Description

User reported that "the agent is not saying hi" despite the session log showing the agent did respond with "Hello! How can I help you today?"

This could indicate one of the following issues:

  1. UI rendering issue: The response was generated but not displayed to the user
  2. Timing/streaming issue: The response may have been truncated or not fully streamed
  3. False positive: User may have reported before the response appeared

Session Evidence

  • Session ID: ses_3eabbfb0bffeWt2tF0WZWfcwYL
  • Session Title: "Casual greeting"
  • Files involved: None (0 files modified)
  • Tools that failed: None
  • Error messages: None

Conversation Log

Role Message
User "hi"
Assistant "Hello! How can I help you today?"
User (empty)
Assistant (empty)

User Feedback

the agent is not saying hi

Analysis

The session data shows the agent DID respond to the greeting. The discrepancy between user feedback and actual session data suggests a potential UI/display issue where the response was recorded server-side but may not have been visible client-side.

Suggested Investigation

  1. Check if there are any UI rendering issues with short responses
  2. Verify streaming/SSE delivery is working correctly
  3. Check if there are browser console errors during message display
Originally created by @kehao95 on GitHub (Jan 31, 2026). Originally assigned to: @rekram1-node on GitHub. ## Context User initiated a casual greeting session to interact with the agent. ## Problem Description User reported that "the agent is not saying hi" despite the session log showing the agent did respond with "Hello! How can I help you today?" This could indicate one of the following issues: 1. **UI rendering issue**: The response was generated but not displayed to the user 2. **Timing/streaming issue**: The response may have been truncated or not fully streamed 3. **False positive**: User may have reported before the response appeared ## Session Evidence - **Session ID**: `ses_3eabbfb0bffeWt2tF0WZWfcwYL` - **Session Title**: "Casual greeting" - **Files involved**: None (0 files modified) - **Tools that failed**: None - **Error messages**: None ### Conversation Log | Role | Message | |------|---------| | User | "hi" | | Assistant | "Hello! How can I help you today?" | | User | (empty) | | Assistant | (empty) | ## User Feedback > the agent is not saying hi ## Analysis The session data shows the agent DID respond to the greeting. The discrepancy between user feedback and actual session data suggests a potential UI/display issue where the response was recorded server-side but may not have been visible client-side. ## Suggested Investigation 1. Check if there are any UI rendering issues with short responses 2. Verify streaming/SSE delivery is working correctly 3. Check if there are browser console errors during message display
Author
Owner

@github-actions[bot] commented on GitHub (Jan 31, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #8564: TUI doesn't render messages from prompt_async endpoint
  • #11289: Empty response bug - add missing await in prompt_async handler
  • #11424: SSE connection always receives message.part.updated events
  • #7882: Archived session 'flashes back' due to SSE race condition
  • #10578: New session UI disappears when stored session list response is late
  • #10998: Run Command message won't display command ran in Zed
  • #7380: Old messages disappear
  • #11062: Web UI reports 'No changes' even after agent has made changes (potential false positive like your case)

The most likely duplicates are #8564 and #11289, which both involve server-side message generation/delivery not reaching the client UI properly.

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Jan 31, 2026): This issue might be a duplicate of existing issues. Please check: - #8564: TUI doesn't render messages from prompt_async endpoint - #11289: Empty response bug - add missing await in prompt_async handler - #11424: SSE connection always receives message.part.updated events - #7882: Archived session 'flashes back' due to SSE race condition - #10578: New session UI disappears when stored session list response is late - #10998: Run Command message won't display command ran in Zed - #7380: Old messages disappear - #11062: Web UI reports 'No changes' even after agent has made changes (potential false positive like your case) The most likely duplicates are #8564 and #11289, which both involve server-side message generation/delivery not reaching the client UI properly. Feel free to ignore if none of these address your specific case.
Author
Owner

@rekram1-node commented on GitHub (Jan 31, 2026):

Can u provide a video?

@rekram1-node commented on GitHub (Jan 31, 2026): Can u provide a video?
Author
Owner

@LiliumSancta commented on GitHub (Jan 31, 2026):

I have the same problem using Kimi 2.5 with Conductor. Whenever the model is waiting for my input with a question, it doesn't appear unless I change sessions and come back again.

@LiliumSancta commented on GitHub (Jan 31, 2026): I have the same problem using Kimi 2.5 with Conductor. Whenever the model is waiting for my input with a question, it doesn't appear unless I change sessions and come back again.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#8168