Mouse wheel stops working after some usage on Windows Terminal

[hhyeon0306]

Description

Mouse wheel scrolling works initially but becomes completely unresponsive after using opencode for a while. Once it stops working, I cannot scroll up to view source code or chat history.

Environment

• OS: Windows 11
• Terminal: Windows Terminal

Steps to Reproduce

1. Launch opencode in Windows Terminal
2. Use it normally for some time (chatting, viewing code, etc.)
3. Try to scroll with mouse wheel

Expected Behavior

Mouse wheel should continue to scroll the content (chat history, source code view).

Actual Behavior

Mouse wheel stops responding entirely. Cannot scroll up to see previous messages or code.

Additional Context

• Wheel works fine initially
• After some usage, it suddenly stops working
• No specific action triggers the issue - it just stops at some point

[github-actions]

This issue might be a duplicate or related to existing mouse/input responsiveness issues on Windows Terminal. Please check:

• Ctrl+C does not disable mouse tracking, causing raw escape sequences to flood terminal (Windows) #6912: Ctrl+C does not disable mouse tracking, causing raw escape sequences to flood terminal (Windows)
• TUI buffer not scrollable when permission is prompted #6901: TUI buffer not scrollable when permission is prompted
• [Bug] TUI scroll position resets to session start after approving commands that exceed terminal height #6895: [Bug] TUI scroll position resets to session start after approving commands that exceed terminal height
• CLI input issues on WSL Ubuntu: no multiline input and copy/paste not working #7297: CLI input issues on WSL Ubuntu: no multiline input and copy/paste not working
• Typing in the prompt input pauses echoing characters occasionally #7240: Typing in the prompt input pauses echoing characters occasionally

These issues all involve input/mouse responsiveness issues in the TUI on Windows Terminal and similar environments. The mouse wheel becoming unresponsive could be related to the mouse tracking system not properly handling state after extended use.

Feel free to ignore if your specific case differs from these issues.