fix(chat): don't send on Enter while the agent is running

[viniciussouzax]

Problem

While an agent response is streaming, pressing Enter sends the typed text
anyway. Sending a new message aborts the in-flight query (chat-bridge
stopSession), so a user's follow-up — often an impatient "are you there?" —
silently kills the very answer they were waiting for. This shows up as the
recurring "Claude Code process aborted by user" message and the impression
that the chat is broken.

Root cause

The keydown handler in AgentChat.tsx calls sendMessage() unconditionally:

if (e.key === 'Enter' && !e.shiftKey) {
  e.preventDefault()
  sendMessage()
}

The Send button is already guarded — it's disabled via
canSend = ... && status !== 'running' — but the Enter shortcut bypasses that
guard entirely.

Fix

Mirror the button's guard in the Enter handler:

if (e.key === 'Enter' && !e.shiftKey) {
  e.preventDefault()
  if (status !== 'running') sendMessage()
}

Shift+Enter (newline) is unaffected.

Testing

• Before: send a message, then press Enter again while it streams → the
  response is aborted ("Claude Code process aborted by user").
• After: pressing Enter while running is a no-op (same as the disabled Send
  button); the streaming response completes normally. Sending works as before
  once the agent is idle.

[sourcery-ai]

Sorry @viniciussouzax, you have reached your weekly rate limit of 500000 diff characters.

Please try again later or upgrade to continue using Sourcery