[DOCS] Environment variables reference missing `CLAUDE_CODE_DISABLE_MOUSE_CLICKS` added in v2.1.195

Status Fixed / completed

Maintainer reply ✓ Yes — bcherny

Activity 3 comments · opened Jun 26, 2026 · closed Aug 17, 2026

💡 Likely answer: A maintainer (bcherny, collaborator) responded on this thread — see the highlighted reply below.

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/env-vars

Section/Topic

The CLAUDE_CODE_DISABLE_* rows of the environment variables table. The new CLAUDE_CODE_DISABLE_MOUSE_CLICKS variable, added in Claude Code v2.1.195 to disable mouse click, drag, and hover in fullscreen mode while keeping wheel scroll, is not listed.

Current Documentation

The environment variables reference lists CLAUDE_CODE_DISABLE_MOUSE and explains it as:

Set to 1 to disable mouse tracking in fullscreen rendering. Keyboard scrolling with PgUp and PgDn still works. Use this to keep your terminal's native copy-on-select behavior

There is no entry for CLAUDE_CODE_DISABLE_MOUSE_CLICKS, so users have no way to discover the new variable from the docs, and no way to learn that it leaves wheel scroll enabled while disabling click/drag/hover.

What's Wrong or Missing?

The release notes for Claude Code v2.1.195 announce the addition of CLAUDE_CODE_DISABLE_MOUSE_CLICKS, a finer-grained companion to CLAUDE_CODE_DISABLE_MOUSE that disables mouse click, drag, and hover while still allowing wheel scroll. The env-vars reference, the fullscreen guide, and the keybindings reference do not mention this variable, so users who want to suppress click/drag/hover without losing wheel scroll cannot find the knob through the documentation.

Suggested Improvement

Add a new row to the CLAUDE_CODE_DISABLE_* section of the environment variables table:

CLAUDE_CODE_DISABLE_MOUSE_CLICKS — Set to 1 to disable mouse click, drag, and hover in fullscreen rendering while keeping wheel scroll. Use this when you want the terminal's native copy-on-select behavior on text but still want to scroll with the mouse wheel. Pair with CLAUDE_CODE_DISABLE_MOUSE=1 to disable all mouse input including wheel. Requires Claude Code v2.1.195 or later.

Cross-reference from the fullscreen guide's "Mouse support" section so users who arrive there from fullscreen rendering docs can find the variable.

Impact

Medium - Makes feature difficult to understand

Additional Context

The release also notes that wheel scroll remains available when only CLAUDE_CODE_DISABLE_MOUSE_CLICKS is set. The current CLAUDE_CODE_DISABLE_MOUSE documentation does not mention this finer-grained split, and the new variable is only discoverable through the release notes.

Affected Pages:
| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/env-vars | Primary location: CLAUDE_CODE_DISABLE_* table |
| https://code.claude.com/docs/en/fullscreen | Should cross-reference the new variable when describing mouse support |
| https://code.claude.com/docs/en/keybindings | Scroll context table mentions fullscreen scrolling; should mention how to opt out of click/drag/hover only |

Total scope: 3 pages affected

View original on GitHub ↗

3 Comments

desclapez · 1 month ago

Can confirm CLAUDE_CODE_DISABLE_MOUSE_CLICKS=1 works as described on v2.1.199 — disables click/drag/hover on interactive option pickers (Select/Confirmation dialogs) while wheel scroll keeps working. Only found out about it via this issue; it's not discoverable anywhere in the shipped docs. +1 for adding it to the env-vars reference.

jmvigorous · 1 month ago

Tested this on Claude Code 2.1.201 inside VS Code's integrated PowerShell terminal (Windows 11).

CLAUDE_CODE_DISABLE_MOUSE_CLICKS=1 did not restore native click-and-drag text selection — plain click+drag still did nothing while Claude Code was running, only Shift+drag forced VS Code's terminal-level selection to work (same as with the var unset).

It also introduced a regression: with the var set, double-click-to-select-word (normally handled locally by VS Code's terminal regardless of an app's mouse mode) stopped working too. Unsetting the var restored double-click immediately, confirming the var itself caused it.

For comparison, CLAUDE_CODE_DISABLE_MOUSE=1 (the older, documented, full-disable variant) does restore click+drag selection, but at a cost beyond "no scroll wheel" — the wheel's motion gets forwarded as Up/Down keystrokes, which at an empty prompt triggers history recall and repopulates the input box with previous submissions. That's a bit more disruptive than the docs description ("keyboard scrolling with PgUp/PgDn still works") suggests.

So right now there's no working middle ground between "Shift+drag required" and "scroll wheel does something unexpected." Flagging in case CLAUDE_CODE_DISABLE_MOUSE_CLICKS is supposed to work differently than observed, or the wheel-to-arrow-key fallback is something that could be scoped out.

bcherny collaborator · 14 days ago

Thanks for flagging this. The environment variables reference now lists CLAUDE_CODE_DISABLE_MOUSE_CLICKS (set to 1 to disable click, drag, and hover in fullscreen mode while keeping wheel scroll; CLAUDE_CODE_DISABLE_MOUSE takes precedence when both are set), and the fullscreen guide mentions it too: https://code.claude.com/docs/en/env-vars

Closing since the docs are updated.

🤖 Generated with Claude Code