Chat UX: queued message lost on interrupt, no immediate-send shortcut, and ESC behavior differs from Claude Code

Aberta
  • Algo errado?
#665 2 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
50/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Pouca atividade
Stack de tecnologia
electron, next.js, typescript
Domínio
desktop, frontend

Direção de pesquisa

Start by locating the chat input and the code that queues messages and interrupts generation; the issue does not name specific files or tests. Reproduce the queued-message loss by typing during generation and pressing ESC or stop, then check how Enter and Ctrl+Enter are handled. Done means queued text is not silently lost and the agreed interrupt-and-send behavior works consistently.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Summary

Three related UX issues with the chat input / message sending behavior in the Codepilot desktop client:

  1. 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.

  2. 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.

  3. 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:

  1. Model is generating a response
  2. User starts typing a new message in the input box (message is queued, shown as pending)
  3. User presses ESC or clicks stop to interrupt the current generation
  4. 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

  1. ESC behavior: Match Claude Code CLI — ESC interrupts generation AND sends the queued message
  2. Ctrl+Enter: Implement as immediate interrupt + send
  3. Queued message preservation: Even if not auto-sent on interrupt, the typed text should be preserved in the input box (not discarded)
  4. 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:

  1. User types a correction/follow-up while model is generating
  2. User interrupts the generation (expecting their queued message to go through)
  3. Message is silently discarded
  4. 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
Linguagem predominante
TypeScript
Estrelas
6.5k
Forks
697
Nenhum PR com merge em 30d

Preparar o ambiente

  • Sem Dockerfile nem arquivo Docker Compose
  • Tem um modelo de pull request
  • Sem guia de contribuição

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de op7418/CodePilot

Todas as issues de op7418/CodePilot

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.