You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bug [Visual]: TUI populated with gibberish upon copying #2256
Upon release of the mouse button after highlighting text to copy, the TUI is populated with gibberish.
Gibberish can be erased by resizing the terminal window.
Writing into the input does not remove the gibberish completely but only overwrites it for the characters that are newly typed out.
Recording.2025-08-26.131307.mp4
This is minor but wanted to make sure it's documented.
Would like to take this opportunity to thank you guys so much for opencode!
I wish I could help better here but I am not really sure I think all the different terminals just have some ansi inconsistencies, there maybe something specific to your config causiing issue but like I said this is all going to be moved to opentui soon and I think one of the problems they at least mentioned attacking is inconsistent ansi between terminals
I'm not sure if this clue is useful, just note it here for now. I will look into this issue again over the weekend.
I tried the following terminal emulators, and all of them can reproduce the issue I mentioned above:
kitty, item2, wezterm, ghostty, rio
However, some other terminals, such as wave, warp, tabby, do not exhibit the aforementioned problem.
The reason I discovered this difference was because I wanted to try using opencode normally on other terminals. Unfortunately, on the corresponding terminals (wave, warp, tabby), I couldn't use some of the keybindings I originally set up in nvim (such as ). (I believe opencode.nvim is a very good way to integrate AI into nvim.) Then I did some research and eventually found Comprehensive keyboard handling in terminals, Comprehensive keyboard handling in terminals. I tried 4 out of the 7 terminals mentioned and was able to reproduce this issue.
in ghostty, it call tell different between and by using cat -v
But I'm not sure if this issue is related to Chinese characters, it doesn't seem like it, but if OpenTUI is going to be an alternative in the future, we might need to pay attention to this aspect. OpenCode itself might not necessarily need such extensive shortcut recognition support (or maybe it could? You can never have too many shortcuts hahaha).
Activity
github-actions commentedon Aug 26, 2025
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
rekram1-node commentedon Aug 26, 2025
that’s so strange, tui is about to get a big overhaul so I hope this will be fixed for you when that gets done
jensenojs commentedon Sep 2, 2025
1 :

2 : select first one
3 : Press comma
using item2 on mac, Monaco Nerd Font. I'm not sure if this type of problem is ultimately tracked under this issue?
rekram1-node commentedon Sep 2, 2025
There is a separate issue that tracks issues w/ Chinese specifically
jensenojs commentedon Sep 3, 2025
tks
jensenojs commentedon Sep 4, 2025
updated : original terminal in mac wii seems ok, So it may be related to some settings of item2. @rekram1-node
Is there any other information I can provide that might help diagnose this problem?
updated : "Gibberish can be erased by resizing the terminal window.", same here
rekram1-node commentedon Sep 4, 2025
I wish I could help better here but I am not really sure I think all the different terminals just have some ansi inconsistencies, there maybe something specific to your config causiing issue but like I said this is all going to be moved to opentui soon and I think one of the problems they at least mentioned attacking is inconsistent ansi between terminals
jensenojs commentedon Sep 16, 2025
I'm not sure if this clue is useful, just note it here for now. I will look into this issue again over the weekend.
I tried the following terminal emulators, and all of them can reproduce the issue I mentioned above:
kitty, item2, wezterm, ghostty, rio
However, some other terminals, such as wave, warp, tabby, do not exhibit the aforementioned problem.
The reason I discovered this difference was because I wanted to try using opencode normally on other terminals. Unfortunately, on the corresponding terminals (wave, warp, tabby), I couldn't use some of the keybindings I originally set up in nvim (such as ). (I believe opencode.nvim is a very good way to integrate AI into nvim.) Then I did some research and eventually found Comprehensive keyboard handling in terminals, Comprehensive keyboard handling in terminals. I tried 4 out of the 7 terminals mentioned and was able to reproduce this issue.
in ghostty, it call tell different between and by using cat -v
But I'm not sure if this issue is related to Chinese characters, it doesn't seem like it, but if OpenTUI is going to be an alternative in the future, we might need to pay attention to this aspect. OpenCode itself might not necessarily need such extensive shortcut recognition support (or maybe it could? You can never have too many shortcuts hahaha).
rekram1-node commentedon Sep 16, 2025
thanks for this, will keep it in mind
fkukuck commentedon Nov 14, 2025
FYI original issue still present in opencode 1.0.61