Random Artifactts In Terminal After Running

[zQueal]

Description

Seems to be tied to mouse movement.

Edition	Windows 10 Enterprise
Version	22H2
Installed on	‎8/‎12/‎2024
OS build	19045.4651
Experience	Windows Feature Experience Pack 1000.19060.1000.0

Shell: Elvish 0.22.0-dev.0.20250105223521-dad2f5cb138c+official

OpenCode version

1.0.185

Steps to reproduce

1. Open opencode, do stuff
2. /exit
3. Continue working -> random artifacts begin showing up

Screenshot and/or share link

Operating System

Windows 10 Enterprise

Terminal

wezterm 20240203-110809-5046fc22

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• Switching branches causes visual artifacts in TUI #5824: Switching branches causes visual artifacts in TUI
• Graphical glitches #5283: Graphical glitches - random TUI artifacts with old text getting stuck
• tui rendering artifacting #1864: TUI rendering artifacting on Windows
• The screen is bugging out with the new "Screen"? Graphic or opencode bug #3541: The screen is bugging out with the new Screen? Graphic or opencode bug (Windows-specific)

Feel free to ignore if none of these address your specific case.

[rekram1-node]

We have a few other issues tracking this. Will fix

[zQueal]

I don't really feel as if they're the same issue. They're both graphical glitches, but mine is literal characters being input into my terminal even after opencode is closed. They're not just visual fragments, they're actual characters tied--for whatever reason--to mouse movement. (moving the mouse more increases the occurrence of these fragments).

The other issues just seem to be random renderings and not actual characters being input into the console.

[rostrovsky]

I have the same issue on Windows Terminal 1.21.3231.0 running git-bash. After closing OC via /exit, any mouse movement (or clicks) inputs text into terminal.

Text is something like:

35;104;31m35;102;30m35;94;26m35 ...

Interestingly I have Ubuntu 22.04 configured in WSL which I use in the exactly same terminal with tmux and zsh and everything works fine there so it doesn't seem to be related to Windows Terminal itself.

[zQueal]

Confirmed still happening in the latest CLI build, as well.