[BUG] Fullscreen TUI still scrolls on bare mouse movement after a wheel notch in urxvt (regression of stale-closed #83487)
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- cli
Research direction
Start by locating the fullscreen renderer's SGR mouse report parser and the handling for motion bit 32 and wheel bit 64; the issue does not name a file or test. Reproduce in urxvt by scrolling one notch, then moving the pointer without touching the wheel. Done when pointer motion alone no longer scrolls, while wheel notches still do.
Written by the indexing model from the issue text.
Description
This report was drafted and filed by Claude Code on the account holder's behalf, at their request.
Summary
#83487 still reproduces on Claude Code 2.1.327. That issue was reproduced and confirmed by a maintainer, then auto-closed as stale without a fix, so I'm re-opening it as a new issue as the bot suggests.
In the fullscreen renderer on urxvt, once the wheel has been scrolled a single notch, every bare mouse movement keeps scrolling the conversation.
Environment
| Claude Code | 2.1.327 |
| Renderer | fullscreen ("tui": "fullscreen") |
| Terminal | rxvt-unicode (urxvt) 9.30, TERM=rxvt-unicode-256color |
| OS | Linux 6.8, X11, i3 |
| tmux | not used |
Reproduction
- Run Claude Code with the fullscreen renderer in urxvt.
- Scroll the mouse wheel one notch.
- Move the mouse without touching the wheel.
Actual: the viewport keeps scrolling as the pointer moves. A left click in the terminal stops it until the next wheel notch.
Expected: the viewport scrolls only on wheel notches.
The same setup in GNOME Terminal does not show the problem.
Cause (from #83487)
I have not re-captured the bytes on this machine; this is the analysis from #83487, which a maintainer confirmed by replaying the sequences. After a wheel notch, urxvt reports pointer motion with both the wheel bit and the motion bit set (ESC [ < 96 ; x ; y M, i.e. 64 | 32), and the fullscreen renderer treats each such report as a wheel notch.
The hardening suggested there still applies: when parsing an SGR mouse report, test the motion bit (32) before the wheel bit (64), since a wheel cannot drag.
- Dominant language
- TypeScript
- Stars
- 156k
- Forks
- 25k
- Avg merge
- 12h 27m
- Merged PRs (30d)
- 4
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from anthropics/claude-code
-
area:agent-sdk area:docs documentation enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
anthropics/claude-code#110914 ·
-
area:desktop area:ui bug platform:macos
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
anthropics/claude-code#110835 ·
-
area:ui bug platform:vscode platform:windows
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
anthropics/claude-code#110675 ·
-
area:hooks area:plugins area:skills enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
anthropics/claude-code#110517 ·
-
area:installation enhancement platform:windows
Difficulty 1/5 Under an hour Newbie friendliness 84/100
anthropics/claude-code#110491 ·
All issues in anthropics/claude-code
Similar issues
-
bot:ai-assisted component:platform-js status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
midnightntwrk/platform-js#69 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Picolab/pico-engine#668 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
ai-driven-qa bug claude Cosmetic
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
needs verification
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 13 days