Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Mouse selection causes input box border lines to wrap and display jumps [1 participants]

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…
GitHub stats
anthropics/claude-code#46287•Fetched 2026-04-11 06:24:17
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
pato-at-krankikompato-at-krankikom
Participants
pato-at-krankikompato-at-krankikom
Timeline (top)
labeled ×3

Error Message

Error Messages/Logs

Fix Action

Fix / Workaround

Workaround: Holding Shift while selecting bypasses tmux mouse handling and avoids the issue.

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

When using mouse selection inside Claude Code running in tmux (with set -g mouse on), the border lines of the input area extend beyond the terminal width, causing them to wrap to the next line. This creates a visible "jump" of ~2 rows in the display.

What Should Happen?

It should not jump :)

<img width="1152" height="135" alt="Image" src="https://github.com/user-attachments/assets/a7edd8db-5bcc-4aee-84f7-c26b2050358e" />

Environment:

  • Claude Code (CLI)
  • Terminal: Ghostty
  • tmux with mouse mode enabled
  • macOS, Apple Magic Trackpad

Error Messages/Logs

Steps to Reproduce

Steps to reproduce:

  1. Run Claude Code inside a tmux session with set -g mouse on
  2. Try to select text with the mouse in or near the input area
  3. The border lines of the input box wrap past the terminal edge, causing the display to shift/jump by 2 rows

Workaround: Holding Shift while selecting bypasses tmux mouse handling and avoids the issue.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.100

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Other

Additional Information

No response

extent analysis

TL;DR

Disable tmux mouse mode or hold Shift while selecting text to avoid the display jump issue.

Guidance

  • Verify that the issue is specific to tmux mouse mode by testing selection without it.
  • Check if the problem persists when using a different terminal or mouse device.
  • Consider configuring tmux to handle mouse events differently, potentially resolving the conflict with Claude Code.
  • Test the workaround of holding Shift while selecting text to confirm it bypasses the issue consistently.

Example

No specific code snippet is applicable in this case, as the issue appears to be related to configuration and interaction between tmux and Claude Code.

Notes

The root cause of the issue seems to be related to how tmux handles mouse events, specifically when selecting text near the input area in Claude Code. The provided workaround suggests that bypassing tmux's mouse handling resolves the issue.

Recommendation

Apply the workaround of holding Shift while selecting text, as it provides a reliable method to avoid the display jump issue without requiring changes to the underlying configuration or software versions.

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…
#api#index setup#retrieval issue#search optimization#API routing

Still need to ship something?

×6

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

Back to top recommendations

TRENDING