Mouse text selection becomes erratic in all panes when Claude Code CLI is running in one pane #10974
Issue DescriptionWhen running Claude Code CLI in one pane of a split-window Ghostty session, mouse text selection becomes erratic and unreliable in all other panes, not just the pane running Claude Code. This suggests Claude Code is affecting Ghostty's global mouse/selection state rather than being isolated to its own pane. The issue isn't limited to the pane where Claude Code is running - text selection breaks in completely separate panes that are just running regular shells or other programs. This cross-pane contamination suggests Claude Code may be sending terminal escape sequences or triggering behavior that affects Ghostty's global mouse event handling. Potentially related issues:
This makes split-pane workflows with Claude Code nearly unusable, as you can't reliably select/copy text from other panes while Claude Code is running. Expected BehaviorMouse text selection should work normally in all panes, regardless of what's running in other panes. Each pane should have isolated mouse/selection state. Actual BehaviorText selection becomes erratic even in panes that are NOT running Claude Code. The selection behavior is unreliable and doesn't work as expected. Reproduction Steps
Ghostty LogsNo response Ghostty VersionOS Version InformationmacOS (latest) (Linux only) Display ServerNone (Linux only) Desktop Environment/Window ManagerNo response Minimal Ghostty Configuration# No special configuration required to reproduce
# Issue occurs with default Ghostty settingsAdditional Relevant ConfigurationClaude Code version: 2.0.50 I acknowledge that:
|
Replies: 6 comments 3 replies
|
I'm seeing this on macOS as well. |
|
Can you please describe "erratic and unreliable" in more specific terms? Can you provide a video of this behavior? |
|
Same thing here on macOS. I'm not using Claude CLI, but I see the same behaviour. I have also noticed that it becomes hard or sometimes impossible to resize the panes and I think it's related. Something with the mouse down state that's stuck. |
|
This is fixed, will be in 1.3.1 |
|
Hitting this regression on /Ghostty 1.3.1 / Build 15212 / commit 332b2ae (macOS), with Claude Code CLI running in one or more splits. Symptoms:
Not fullscreen-specific (reproduces in windowed mode). Because the trigger is a plain mouseDown (no drag, no release-over-text), this looks less like a stuck "button-held" state and more like the mouseDown handler is failing to reset the selection anchor on subsequent clicks, while mouseDragged/mouseUp continue to fire normally against the stale anchor. The fact that selection anchoring, focus-follows-mouse, and ⌘+hover URL activation all break together — and all recover together on a Space switch — suggests the whole mouse/hover event pipeline for the window is getting gated off after the first click, not just the selection state machine. A full app reactivation cycle clears it; losing/regaining key-window focus within the same Space does not. Happy to capture ghostty +show-config, traces, or test a patch build if helpful. |
|
Still reproducible on 1.3.1 stable (macOS) Ghostty 1.3.1, channel: stable Setup: one window with multiple splits, each attached to remote sessions (zmx over SSH). focus-follows-mouse = true is set. Symptoms match this thread exactly:
This has been persistent for months across 1.2 → 1.3.1. Happy to provide more debug info if useful. |
This is fixed, will be in 1.3.1