[Feature Request] Add granular mouse control options to disable click-selection while preserving scroll

[typedev]

Bug Description
Split mouse controls: allow disabling click-to-select in menus while keeping scroll

The recent change "Added mouse click support to select menus" makes interactive menus selectable by mouse click. I find the click-to-select behavior disruptive, but I want to keep mouse-wheel scrolling and auto-scroll, which I rely on.

Right now this is all-or-nothing: CLAUDE_CODE_DISABLE_MOUSE=1 disables click selection but also kills scroll-wheel support, so there's no way to keep one without the other.

Request: a granular toggle to control mouse features independently — e.g. a settings.json option like menuClickSelectEnabled: false (or separate mouse.scroll / mouse.click flags) so users can disable menu click-selection while preserving scroll.

Environment Info

• Platform: linux
• Terminal: vte-based
• Version: 2.1.190
• Feedback ID: 8e97d75d-ff76-4703-8235-bf87fce48d7d

Errors

[]

[viperaykiri]

+1 for this. Concrete use case: on Windows (cmd/conhost, v2.1.191) the mouse wheel is the natural way to scroll back through the conversation. The only workaround for accidental click-accept in dialogs (permission/confirmation prompts and the option selector) is CLAUDE_CODE_DISABLE_MOUSE=1, but that is all-or-nothing — it also kills wheel scrolling, forcing PageUp/PageDown. A granular toggle (e.g. CLAUDE_CODE_DISABLE_MOUSE_CLICKS=1 or mouse.clickSelect: false) that disables click-selection while preserving wheel scroll would solve this cleanly. Related: #70539.

[hoiung]

Strong +1 on this. My exact use case: I click in the terminal the normal way to move focus and select text so I can type, and the CLI captures those clicks and selects an option on the interactive prompts (AskUserQuestion menus, permission dialogs). A stray click submits an answer I never meant to pick, so I have to interrupt, cancel the wrong answer, and get the question re-asked. Net result is slower than no mouse support at all.

The one part I do want to keep is click-to-position-cursor in the input line (saves deleting whole sentences or arrow-keying across). Today the only off-switch is CLAUDE_CODE_DISABLE_MOUSE=1, which is all-or-nothing and takes that away too. A granular mode (e.g. CLAUDE_CODE_MOUSE_MODE=cursor-only: keep cursor positioning, disable click-selection on menus) would fix it. At minimum, a mouse-selected decision should require a confirm rather than firing on first click.

[daltonch]

Strong +1 on this as well. I'm on a mac, not that it matters, but clicking back to select the terminal in focus so i can use my keyboard sometimes select's an option I DO NOT WANT, wasting tokens. Clicking to select from a menu in a terminal is really bad UX.

[L0g0ff]

Please please fix this! I have already accidentally allowed SSH * and that is not what I want on production environments... And disable the CLAUDE_CODE_DISABLE_MOUSE=1 don't allow me to copy from my terminal anymore.

[real-worlds]

annoying

[bsims-codes]

mouse click support to select menus was a stupid feature in the first place.

[stephclay]

+1 for this. It is way to easy too click in a terminal to bring it to the foreground and accidentally select a random option from a list. As stated above, this could lead to production issues.

[andemattwork]

Help! Please give us more granular mouse settings. I'm constantly focusing the terminal window with a click and errantly selecting a choice.