You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Agent response not visible to user despite responding correctly #11512
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:
UI rendering issue: The response was generated but not displayed to the user
Timing/streaming issue: The response may have been truncated or not fully streamed
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
Check if there are any UI rendering issues with short responses
Verify streaming/SSE delivery is working correctly
Check if there are browser console errors during message display
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.
Activity
github-actions commentedon Jan 31, 2026
This issue might be a duplicate of existing issues. Please check:
/session/:id/messageor/session/:id/prompt_async, always recv themessage.part.updatedby SSE connection #11424: SSE connection always receives message.part.updated eventsThe 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.
rekram1-node commentedon Jan 31, 2026
Can u provide a video?
VitorNaidek commentedon 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.
emuminov commentedon Mar 9, 2026
Same thing happens with
agent-shellin emacs when OpenCode ACP is used:xenodium/agent-shell#384
Judging by the logs in Emacs, the issue is that the responses are out of order.
github-actions commentedon May 9, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.