Can't open TUI running on a remote Omnissa Horizon machine

[fdittz]

Description

When I try opening opencode on this remote machine(Omnissa Horizon) running Red Hat 8 and Gnome 3.32, using gnome-terminal, I get a black screen with the string >4;1m Gi=31337,s=1,v=1,a=q,t=d,f=24;AAAA and it freezes, I cant ctrl+c or ctrl+z out of it, seems that it tries to print the starting screen and fails.

I tried with kitty and I don't get this string, just a blank screen, but i'm getting the following on STDERR
[4.535] [PARSE ERROR] Unsupported screen mode: 2027 (private)

Tried WezTerm and tmux, no luck. Also tried running on a container and the same issue happens. Is there anything I can do on my remote machine to solve this?

Plugins

No response

OpenCode version

1.1.30

Steps to reproduce

No response

Screenshot and/or share link

Operating System

Red Hat Enterprise Linux release 8.10 (Ootpa), GNOME Shell 3.32.2

Terminal

gnome-terminal, kitty, wezterm, tmux

[github-actions]

This issue might be a duplicate of or related to existing terminal rendering issues. Please check:

• Garbled characters appear after launching the program on Windows system. #9814: Garbled characters appear after launching the program on Windows system
• TUI rendering with random characters like â and € windows 11 when UV formatter is enabled #9338: TUI rendering with random characters like â and € on Windows 11
• The Windows Terminal interface is not displaying correctly after answering a question. #9798: The Windows Terminal interface is not displaying correctly after answering a question
• Something is wrong with the terminal UI. It feels like there is a shadow covering the display. #9823: Something is wrong with the terminal UI - shadow covering the display
• the ui is broken when running on built-in terminal #9750: The UI is broken when running on built-in terminal (macOS)
• [BUG] The TUI is merging lines of text when the terminal window is small #9899: The TUI is merging lines of text when the terminal window is small
• Desktop app fails to start on Linux/Wayland - 'open terminal failed: not a terminal' #9505: Desktop app fails to start on Linux/Wayland - terminal-related errors

The core issue appears to be related to terminal capability detection or screen mode negotiation, particularly with the ANSI escape sequences: >4;1m\n\Gi=31337,s=1,v=1,a=q,t=d,f=24;AAAA and parse errors about "Unsupported screen mode: 2027 (private)". This suggests a potential incompatibility with certain terminal emulators or terminal configurations, particularly on remote machines with GNOME 3.32.

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

[KevinWang676]

ran into the same issue here on my windows machine

[fdittz]

Seems that its not an issue with TUI, but with bun running on NFS. As I'm using a horizon remote terminal, all directories I have access to are NFS shares, so bun has troubles with the hardlinks and fails with FileNotFoundError.

The issue #4442 describes it perfectly, adding --backend=copyfile to the install and add commands solved my issue on a fortk, I wonder if we could have it set by an envvar?

[github-actions]

To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.