Summary
Three related UX issues with the chat input / message sending behavior in the Codepilot desktop client:
-
Queued message lost on interrupt: When the user types a message while the model is still generating (message is queued), then presses ESC or clicks stop to interrupt the current generation, the queued message is silently discarded instead of being sent.
-
No immediate-send (interrupt + send) shortcut: In Claude Code CLI, Ctrl+Enter sends the message and immediately interrupts the current generation. In Codepilot, there appears to be no equivalent — the user can only queue messages, and there's no way to force-send with immediate interruption.
-
No interrupt-and-send button: Unlike Cursor (which has a visible "send anyway / interrupt" button that appears when you type during generation), Codepilot only shows a "cancel" action for queued messages, but no way to promote a queued message to an immediate interrupt-and-send.
Detailed description
1. Queued message lost on interrupt
Steps to reproduce:
- Model is generating a response
- User starts typing a new message in the input box (message is queued, shown as pending)
- User presses ESC or clicks stop to interrupt the current generation
- The queued message disappears without being sent
Expected behavior:
- Pressing ESC while a message is queued should: interrupt the current generation AND send the queued message (matching Claude Code CLI behavior)
- OR at minimum, the typed text should be preserved in the input box so the user can re-send it manually
Actual behavior:
- The queued message is silently discarded. The user cannot recover the text they typed — it's not preserved in the input box, not in clipboard, not in any history.
2. No immediate-send shortcut
Expected behavior (from Claude Code CLI):
Enter → queue the message (send after current generation completes)
Ctrl+Enter → immediately interrupt current generation and send the message
Actual behavior in Codepilot:
Enter queues the message (works)
Ctrl+Enter behavior is unclear or non-functional as an interrupt-and-send
- No visible keyboard shortcut hint for immediate send
3. No interrupt-and-send affordance
Expected behavior (from Cursor):
- When user types while generation is active, a visible button appears: "Send anyway" / "Interrupt and send"
- This gives the user a clear choice: queue or force-send
Actual behavior in Codepilot:
- Only a "cancel queue" option is shown
- No way to promote queued text to an immediate send
Suggested improvements
- ESC behavior: Match Claude Code CLI — ESC interrupts generation AND sends the queued message
- Ctrl+Enter: Implement as immediate interrupt + send
- Queued message preservation: Even if not auto-sent on interrupt, the typed text should be preserved in the input box (not discarded)
- Visual affordance: Consider adding an "Interrupt and send" button that appears when the user types during generation (similar to Cursor's pattern)
Related UX principle
The current behavior creates a frustrating loop:
- User types a correction/follow-up while model is generating
- User interrupts the generation (expecting their queued message to go through)
- Message is silently discarded
- User has to retype everything from memory
This is particularly painful for long or carefully crafted messages.
Environment
- Codepilot version: 0.64.0
- Platform: Windows 11
Summary
Three related UX issues with the chat input / message sending behavior in the Codepilot desktop client:
Queued message lost on interrupt: When the user types a message while the model is still generating (message is queued), then presses ESC or clicks stop to interrupt the current generation, the queued message is silently discarded instead of being sent.
No immediate-send (interrupt + send) shortcut: In Claude Code CLI,
Ctrl+Entersends the message and immediately interrupts the current generation. In Codepilot, there appears to be no equivalent — the user can only queue messages, and there's no way to force-send with immediate interruption.No interrupt-and-send button: Unlike Cursor (which has a visible "send anyway / interrupt" button that appears when you type during generation), Codepilot only shows a "cancel" action for queued messages, but no way to promote a queued message to an immediate interrupt-and-send.
Detailed description
1. Queued message lost on interrupt
Steps to reproduce:
Expected behavior:
Actual behavior:
2. No immediate-send shortcut
Expected behavior (from Claude Code CLI):
Enter→ queue the message (send after current generation completes)Ctrl+Enter→ immediately interrupt current generation and send the messageActual behavior in Codepilot:
Enterqueues the message (works)Ctrl+Enterbehavior is unclear or non-functional as an interrupt-and-send3. No interrupt-and-send affordance
Expected behavior (from Cursor):
Actual behavior in Codepilot:
Suggested improvements
Related UX principle
The current behavior creates a frustrating loop:
This is particularly painful for long or carefully crafted messages.
Environment