Ctrl+C doesn't work in Ghostty when running Open Code or Claude Code.

[XDreamc]

Issue Description

However, when running Open Code or Claude Code in Ghostty, pressing Ctrl+C fails to exit the program. I tested the same commands in iTerm2 and they work fine, so I have ruled out issues with Open Code and Claude Code themselves.

Expected Behavior

Ctrl+C ：Quit Open Code or Claude Code

Actual Behavior

Nothing happens

Reproduction Steps

1. Launch Ghostty.
2. Execute opencode or claude code.
3. When the interface appears, press Ctrl+C. (Nothing happens)

Ghostty Logs

No response

Ghostty Version

Ghostty 1.3.1

Version
  - version: 1.3.1
  - channel: stable
Build Config
  - Zig version   : 0.15.2
  - build mode    : .ReleaseFast
  - app runtime   : .none
  - font engine   : .coretext
  - renderer      : renderer.generic.Renderer(renderer.Metal)
  - libxev        : kqueue

OS Version Information

macOS 13.7.8 (22H730)

(Linux only) Display Server

None

(Linux only) Desktop Environment/Window Manager

No response

Minimal Ghostty Configuration

None

Additional Relevant Configuration

No response

I acknowledge that:

• I have reviewed the FAQ and confirm that my issue is NOT among them.
• I have searched the Ghostty repository (both open and closed Discussions and Issues) and confirm this is not a duplicate of an existing issue or discussion.
• I have checked the "Preview" tab on all text fields to ensure that everything looks right, and have wrapped all configuration and code in code blocks with a group of three backticks (```) on separate lines.

[mitchellh]

These work for me just fine, I just tried both on macOS and Linux. More information required to diagnose.

[XDreamc]

Open Ghostty on an Intel-based MacBook Pro.
I have already tried reinstalling the system, but the issue persists.
Here are the diagnostic logs captured while running with /Applications/Ghostty.app/Contents/MacOS/ghostty --debug-input:
Bash: opencode

Actual:
SEL: insertNewline:

Pressing Control + C (inside opencode):
Expected: Terminate process / SIGINT
Actual:
SEL: noop:
SEL: noop:
SEL: noop:
SEL: noop:
SEL: noop:
SEL: noop:
SEL: noop:
Pressing Control + P (inside opencode):
Expected: Scroll up / Page Up
Actual:
SEL: moveUp:
SEL: moveUp:
SEL: moveUp:
SEL: moveUp:
SEL: moveUp:
SEL: moveUp:

[XDreamc]

Sorry， intel macbook pro

Issue Description
The Control key (Ctrl) does not function when running specific applications like claude-code or open-code inside Ghostty. This results in being unable to send SIGINT (via Ctrl+C) to terminate processes or use other control shortcuts (like Ctrl+P).

Expected Behavior
Attempt to press Control + C.

Expected Result: The process should terminate (or the shortcut should work).
Actual Behavior
Actual Result: Nothing happens. The Control key press is ignored.
Reproduction Steps
Open Ghostty on an Intel-based MacBook Pro.
Launch claude-code or open-code.
Attempt to press Control + C.
Expected Result: The process should terminate (or the shortcut should work).
Actual Result: Nothing happens. The Control key press is ignored.
Additionally, navigation shortcuts like Control+P inside these editors do not work.

[XDreamc]

@mitchellh intel macbook pro 。It always reproduces, even after reinstalling. Pressing Control + any key has no effect in Claude Code and CodeX

[LuckyQ7]

I’m seeing a similar issue on Apple Silicon as well.

• MacBook Pro with Apple M1 Pro
• macOS 13.7.8 (22H730)
• Ghostty 1.3.1, Build 15212, Commit 332b2ae
• Shell: zsh
• Affected app: Codex TUI

For me, Ctrl+C and Ctrl+V can work when Ghostty/Codex is first opened, but after using it for a while they stop working reliably. Ctrl+C no longer cancels/interruption inside Codex,
and Ctrl+V no longer pastes reliably. Opening a fresh Ghostty session seems to make it work again temporarily.