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
[FEATURE]: Add safe TUI rendering mode for old Windows conhost terminals #28324
I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
OpenCode may render incorrectly in old Windows console environments where Windows Terminal is unavailable or cannot be installed, such as Windows versions before Windows Terminal support, classic conhost.exe, and terminal wrappers based on the old console stack such as Cmder / ConEmu.
In these environments, users may see problems such as:
Raw ANSI escape sequences being printed
Broken or garbled TUI layout
Incorrect colors or missing styles
Rendering behavior that works in modern Windows Terminal but fails in classic conhost-based terminals
This is not mainly a request for broad terminal feature detection. The main issue is that some users are still on older Windows environments where they cannot simply switch to Windows Terminal, so OpenCode should provide a safer rendering fallback for old conhost-based terminals.
Expected behavior:
Detect classic Windows conhost.exe or old conhost-based terminal wrappers when possible
Enable compatible ANSI / VT behavior when the system supports it
Avoid using rendering features that are unreliable in old Windows console hosts
Fall back to a simpler rendering mode when full TUI rendering is not reliable
Show a clear warning if the current terminal is known to have limited rendering support
#23718 is the closest related issue, but this request is slightly broader. The main point here is not only that Cmder fails, but that old Windows environments without Windows Terminal support still rely on classic conhost.exe or conhost-based wrappers such as Cmder / ConEmu.
For those environments, users cannot always switch to Windows Terminal. So the request is for a safer TUI rendering fallback for old conhost-based terminals, rather than a fix for one specific Cmder regression.
#21277 and #26480 are also related Windows terminal issues, but they focus on crash cleanup / ConPTY exit behavior. This issue is specifically about rendering compatibility and fallback behavior for old Windows conhost environments.
Activity
github-actions commentedon May 19, 2026
This issue might be a duplicate of existing issues. Please check:
Water-Run commentedon May 19, 2026
#23718 is the closest related issue, but this request is slightly broader. The main point here is not only that Cmder fails, but that old Windows environments without Windows Terminal support still rely on classic
conhost.exeor conhost-based wrappers such as Cmder / ConEmu.For those environments, users cannot always switch to Windows Terminal. So the request is for a safer TUI rendering fallback for old conhost-based terminals, rather than a fix for one specific Cmder regression.
#21277 and #26480 are also related Windows terminal issues, but they focus on crash cleanup / ConPTY exit behavior. This issue is specifically about rendering compatibility and fallback behavior for old Windows conhost environments.
github-actions commentedon Jul 19, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.