UI chat: "New messages loaded" notification can incorrectly block sending the next message #2033

When using the kagent UI chat, attempting to send a new message can show this notification instead of sending the message:

New messages loaded — please review before sending

This happens even when the chat appears up to date and there are no obvious new messages that need review. From the user's perspective, the conversation is ready, but the first send attempt is blocked. Retrying the same send action usually succeeds.

This has been observed during normal same-tab usage, after receiving a completed response and then trying to send the next message.

Screenshot

Steps to reproduce

1. Open the kagent UI in Chrome on macOS.

2. Start or open a chat session with an agent.

3. Send a message and wait for the agent response to complete.

4. Type another message.

5. Try to send it using either:

   • Cmd+Enter, or
   • the Send button.

6. Observe that the message may not send. Instead, a toast appears:

   New messages loaded — please review before sending

7. Try sending the same message again.

8. The second attempt usually succeeds.

Expected behavior

If the user is already viewing the latest messages in the current chat, pressing Send or using Cmd+Enter should send the message immediately.

The "New messages loaded" warning should only appear when there are actually unseen messages or session changes that the user needs to review before sending.

Actual behavior

The UI sometimes blocks the first send attempt and shows:

New messages loaded — please review before sending

The user then has to retry the send action for the message to go through.

Impact

This makes the chat input feel unreliable because a normal send action can appear to fail even though the chat is ready. It affects both keyboard submission and clicking the Send button.

Workaround

Retry the send action after the notification appears. The second attempt usually succeeds.

Environment

• kagent version / commit: latest main as of 2026-06-16, observed around 67431ef6
• Deployment method: kagent UI from current upstream/main build
• Browser: Chrome
• OS: macOS
• Chat path: regular kagent UI chat session
• Repro context: most noticeable after an agent response completes and the user sends the next message in the same chat

Additional notes

The warning is useful when another tab or client updates the session and the user genuinely needs to review new content before sending. The problem is that it can also appear during normal same-tab usage where the latest response is already visible.