Chat UX: queued message lost on interrupt, no immediate-send shortcut, and ESC behavior differs from Claude Code
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 50/100
- issue の種類
- 機能追加
- 明瞭さ
- おおむね明確
- 活発さ
- 静か
- 技術スタック
- electron, next.js, typescript
調査の方向性
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.
索引モデルが issue の本文から書いたものです。
説明
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:
- 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:
Enterqueues the message (works)Ctrl+Enterbehavior 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
- 主要言語
- TypeScript
- スター
- 6.5k
- フォーク
- 697
- PR マージ指標
- 30日以内にマージされた PR はありません
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドなし
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
op7418/CodePilot のほかの issue
-
发生错误时提醒Error:successオープンbug P0-crash-or-interrupt
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
-
難易度 2/5 1〜3時間 初心者へのやさしさ 65/100
-
Effort selector dropdown hidden for GLM models — blocks access to GLM-5.2 High/Max effort tiersオープン
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
-
bug P0-crash-or-interrupt
難易度 4/5 3〜5日 初心者へのやさしさ 48/100
op7418/CodePilot の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
backnotprop/plannotator#2914 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
microsoft/vscode-containers#655 ·
メンテナーはふだん 1 日以内に返信
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 77/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
dsh-tauri-desk/deepseek-harness-desktop#1477 · コメント 1 件 ·