OpenCode TUI Chinese Text Display Issue

[darkmanno6]

Description

After upgrading OpenCode TUI to version 1.1.13, Chinese characters cannot be displayed properly（）. However, they display correctly in version 1.1.8.
It will be displayed if the mouse selects it; otherwise, it will not be displayed, as shown in the figure.

Environment

• Operating System: macOS
• Terminal: iTerm2
• OpenCode Version:
  • 1.1.8: ✅ Chinese characters display normally
  • 1.1.13: ❌ Chinese characters cannot be displayed
• Installation Method: bun add -g opencode-ai
• Terminal Font: Font that supports Chinese (Chinese text displays normally in other applications)

Additional Information

• Terminal encoding is set to UTF-8
• iTerm2 font supports Chinese (Chinese text displays normally in other system applications)
• Pure English messages display normally in both versions

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

[github-actions]

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

• Chinese text in background chat disappears when Ctrl+P command menu is open #7650: Chinese text in background chat disappears when Ctrl+P command menu is open - Related to Chinese character rendering issues in v1.1.12
• Unicode character in line causing rendering to count characters incorrectly #5763: Unicode character in line causing rendering to count characters incorrectly - Similar character rendering problem affecting display
• Korean (Hangul) characters display as broken/garbled in input field #3493: Korean (Hangul) characters display as broken/garbled in input field - CJK character rendering issue affecting visibility
• Unescaped binary response scrambles TUI, possible code injection #6216: Unescaped binary response scrambles TUI, possible code injection - Binary/character scrambling issues in TUI

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

[kommander]

Can you try running the debug version like OC_NO_KITTY_KEYBOARD=1 bunx opencode-ai@snapshot-kmdr-debug? Or try it in a terminal that does not support kitty keyboard, like Alacritty. I need to know if it is an issue with kitty keyboard input.

[darkmanno6]

Can you try running the debug version like OC_NO_KITTY_KEYBOARD=1 bunx opencode-ai@snapshot-kmdr-debug? Or try it in a terminal that does not support kitty keyboard, like Alacritty. I need to know if it is an issue with kitty keyboard input.

it works on Alacritty.
and I've noticed that different themes also affect this issue. For example, the system theme exhibits this problem, while some others like ayu do not.

Additionally, there seem to be some issues with the theme colors. I remember that the Materia theme is a dark theme, but now it's appearing as a light theme.

[kommander]

Could you try bunx opencode-ai@snapshot-kmdr-debug again if that input issue still happens in the terminal it happened before?

[darkmanno6]

Could you try bunx opencode-ai@snapshot-kmdr-debug again if that input issue still happens in the terminal it happened before?

yes ,it still happened

[kommander]

Weird. Did you try without any plugins, like without OMO?

[darkmanno6]

Weird. Did you try without any plugins, like without OMO?

I t ry it without omo , and still happened

and i have found that it worked ok in the vscode terminal

[kommander]

I want to get to the bottom of this. Can you get the opentui examples app from https://github.com/anomalyco/opentui/releases/download/v0.1.72/opentui-examples-v0.1.72-windows-x64.zip and run the "Keypress Debug Tool", type a few characters that cause problems in the prompt textarea, then trigger shift+s (sorry, western keybinding at the moment), which should create a json log file in the CWD with some info. Please share that.

[darkmanno6]

I want to get to the bottom of this. Can you get the opentui examples app from https://github.com/anomalyco/opentui/releases/download/v0.1.72/opentui-examples-v0.1.72-windows-x64.zip and run the "Keypress Debug Tool", type a few characters that cause problems in the prompt textarea, then trigger shift+s (sorry, western keybinding at the moment), which should create a json log file in the CWD with some info. Please share that.

sorry，the app you provided is an .exe program, which I cannot use on my Mac system