Codex and Claude on Mac: Windows-style copy, paste and terminal interrupt
By Wondering Works, maker of Windsify · Updated
In Codex and Claude desktop chat, Windsify 1.4.21 provides ordinary Windows-style shortcuts such as Ctrl+C to copy and Ctrl+V to paste in both Free and Pro. In a recognized embedded terminal with Pro, use Ctrl+Shift+C or Ctrl+Insert to copy; Ctrl+C stays native interrupt, even with a selection.
Free terminal warning: Free uses generic Windows mappings inside embedded terminals too. Ctrl+C copies and does not interrupt. If Pro does not recognize an embedded terminal, it may also apply chat copy behavior to Ctrl+C. Check the focused pane before relying on an interrupt.
The focused pane and edition determine the shortcut
| Where you are | Shortcut | Result |
|---|---|---|
| Desktop chat, Free or Pro | Ctrl+C · Ctrl+V | Ordinary copy and paste mappings |
| Embedded terminal, Free | Ctrl+C · Ctrl+V | Generic copy and paste; Ctrl+C does not interrupt |
| Recognized embedded terminal, Pro | Ctrl+Shift+C · Ctrl+Insert | Native copy action for selected terminal text |
| Recognized embedded terminal, Pro | Ctrl+V · Ctrl+Shift+V · Shift+Insert | Native paste action |
| Recognized embedded terminal, Pro | Ctrl+C | Native interrupt, including when text is selected |
| Recognized standalone Terminal or iTerm2, either edition | Control shortcuts | Remain native |
Pro chat also retains ordinary editing mappings when the focused area cannot be classified. This includes Ctrl+A, Ctrl+C/V/X, undo/redo and text navigation. Only a confirmed terminal selects Pro terminal rules. In that recognized terminal, other shell Control keys, including Ctrl+A/E/D/L/R/Z, stay native; the shell or running program determines their response.
Set up and test a safe clipboard example
- Install Windsify 1.4.21, allow Accessibility access, and enable Windows keyboard shortcuts. Check that Pro or the 14-day Pro trial is active if you need embedded-terminal interrupt behavior.
- Click the desktop chat input. Copy and paste a harmless test sentence with Ctrl+C/V; ordinary selection behavior still belongs to the app.
- In an available embedded terminal, click the actual shell input rather than a Find field or static output. With Pro, select harmless output and copy it with Ctrl+Shift+C or Ctrl+Insert.
- Paste harmless text with Ctrl+V without executing it. Test Ctrl+C on a disposable foreground command, and confirm it interrupts rather than copying.
No Codex or Claude settings or app files are modified by this adapter. This guide concerns the desktop apps and their recognized embedded terminals. Running the Claude Code CLI in a separate terminal does not create Claude desktop-pane integration; that terminal follows its own native policy.
Why Ctrl+C does not copy a terminal selection in Pro
Codex and Claude do not use Windsify’s VS Code selection-aware integration. In a recognized Pro terminal, Ctrl+C interrupts even while output is selected. Use an explicit copy chord instead. The VS Code terminal guide explains its separate setup, where selected text can make Ctrl+C copy and no selection can make it interrupt.
If copying or interrupting behaves differently
- Check Free versus Pro. A Free embedded terminal maps Ctrl+C to copy. Pro terminal shortcuts require an active trial or license.
- Move focus into the shell input. A visible terminal beside a focused chat input is not terminal focus. Find fields, static output and incomplete focus information do not establish it either.
- If a terminal is not recognized, recover safely. Disable Windows keyboard translation for native behavior, or use a recognized standalone Terminal or iTerm2 window. Use Shortcut Help to inspect the shortcut and review the report before sharing it.
- Compare with native Command+C/V. If native clipboard actions fail too, check the desktop app itself. A mapping cannot repair a broken native action.
- Check native-input guards. Secure input, explicit exclusions and remote guards retain native behavior. See Codex and Claude support for troubleshooting.
How terminal focus is identified
Classification uses accessibility roles, interface classes and the ancestry of the focused element. It does not read messages, terminal text, selected-text contents or clipboard contents. Changed focus, missing metadata or a query timeout can leave classification unknown; Pro then uses ordinary chat mappings, so an unrecognized terminal may receive copy instead of interrupt.
Windsify 1.4.21 improves chat shortcuts when Codex or Claude focus cannot be identified. See the release notes. If behavior changes after a desktop-app update, use the troubleshooting steps above.
Frequently asked questions
Does Ctrl+C copy or interrupt in Codex and Claude terminals?
In a recognized Pro embedded terminal, Ctrl+C interrupts even with selected text. Use Ctrl+Shift+C or Ctrl+Insert to copy. Free uses generic Ctrl+C copy; an unrecognized Pro terminal may also receive chat copy behavior.
Is this the same selection-aware behavior as VS Code?
No. Selection-aware Ctrl+C belongs to the configured VS Code Pro integration. Codex and Claude Pro terminals use explicit copy chords and native Ctrl+C interrupt.
What should I do if Pro does not recognize the terminal?
Disable Windows keyboard translation to use native behavior, or use a recognized standalone Terminal or iTerm2 window. Use Shortcut Help to inspect the unexpected shortcut and review its report before sharing it.
The download includes a 14-day full Pro trial; Free features remain after it ends. Pro is currently US$14.99 early bird, regularly US$19.99, paid once for up to 3 Macs with all future updates. See pricing.