claude-code - 💡(How to fix) Fix Ctrl+C does not copy selected text in Claude desktop app — always interpreted as 'stop generating'

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
RAW_BUFFERClick to expand / collapse

Ctrl+C does not copy selected text in Claude desktop app — always interpreted as "stop generating"

Environment

  • App: Claude desktop (Windows, MSIX install from Microsoft Store)
  • Version: 1.7196.0.0
  • Install path: C:\Program Files\WindowsApps\Claude_1.7196.0.0_x64__pzs8sxrjxfjjc\app\Claude.exe
  • OS: Windows 11 Pro 10.0.26200

Steps to reproduce

  1. Open a conversation that has at least one response from Claude.
  2. Click-and-drag to highlight a span of text inside a message bubble (assistant or user).
  3. With the selection still visible, press Ctrl+C.

Expected behavior

The selected text is copied to the system clipboard. This is the universal Windows convention used by browsers, IDEs, File Explorer, Notepad, and — most relevantly — Windows Terminal, which adopted the convention "Ctrl+C copies if a selection exists, otherwise it sends interrupt."

Actual behavior

Ctrl+C is captured by the app as "stop generating" (or silently swallowed when no generation is active). The clipboard is not updated. The only ways to copy are:

  • Right-click → Copy on the selection
  • The hover-revealed Copy button on a message bubble, which copies the entire message rather than the selected span

Suggested fix

When the focused element has a non-empty text selection, defer to the standard clipboard path (document.execCommand("copy") or the Clipboard API) instead of routing Ctrl+C to the interrupt handler. Otherwise, fall through to the existing "stop generating" behavior. This mirrors Windows Terminal's copyOnSelect/Ctrl+C resolution and matches user expectation from every other Windows app.

Impact

Copying snippets — code, command names, URLs, extension names — out of Claude's responses is a many-times-per-session operation. The current binding forces users to switch to mouse-based copying for what is otherwise muscle-memory keyboard work, and the whole-message Copy button can't substitute when only a partial selection is wanted.

Notes

  • Reproduces on a fresh window with no in-flight generation, so it isn't only the "interrupt during stream" case.
  • The Ctrl+Shift+C and Ctrl+Insert paths also do not copy (worth confirming during triage).

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

The selected text is copied to the system clipboard. This is the universal Windows convention used by browsers, IDEs, File Explorer, Notepad, and — most relevantly — Windows Terminal, which adopted the convention "Ctrl+C copies if a selection exists, otherwise it sends interrupt."

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Ctrl+C does not copy selected text in Claude desktop app — always interpreted as 'stop generating'