[Bug] Mouse drag-to-select intercepted by click-to-copy functionality in CLI
Bug Description
Mouse text selection is broken in this Claude Code CLI session: click-and-drag is intercepted as click-to-copy instead of doing normal native terminal text selection. This is a severe usability regression. Drag-to-select is a fundamental terminal interaction, and having it hijacked is genuinely disruptive — I could not select any text in the conversation.
Notably, I am NOT seeing this behavior in my other Claude Code CLI sessions, which suggests it's a recent, experimental, or session-scoped change rather than a long-standing default. There is no documented way to disable it.
Please either revert this, make it opt-in (off by default), or add a config/settings toggle to disable mouse capture / click-to-copy so native terminal text selection works again. As it stands the pattern is actively hostile to normal terminal workflow.
Environment Info
- Platform: linux
- Terminal: vscode
- Version: 2.1.207
- Feedback ID: 0c152e5a-b417-4120-ac77-a8c78d7a1160
Errors
[]
3 Comments
Agreed. Click-to-copy causes so many headaches for me. I want to opt out.
Confirmed what you're seeing on 2.1.233 (Linux): in fullscreen rendering mode Claude Code captures mouse events, so click-and-drag makes a selection inside Claude Code (auto-copied to your clipboard on release) instead of a native terminal selection. Your other sessions behaved differently because fullscreen rendering was rolling out gradually at the time.
This is intended behavior with documented opt-outs:
Shiftwhile dragging (VS Code/Cursor; other terminals listed in the docs)./config.CLAUDE_CODE_DISABLE_MOUSE=1(keeps flicker-free rendering; native selection works again), orCLAUDE_CODE_DISABLE_MOUSE_CLICKS=1to keep wheel scrolling but drop click/drag handling.Docs: https://code.claude.com/docs/en/fullscreen#keep-native-text-selection
Closing as intended behavior — reply to reopen if the opt-outs don't cover your workflow.
🤖 Generated with Claude Code
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.