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

Activity

1. fdittz

   added

   bugSomething isn't workingSomething isn't working

   on Jan 21, 2026
2. github-actions

   assigned

   kommander

   on Jan 21, 2026
3. github-actions

   added

   opentuiThis relates to changes in v1.0, now that opencode uses opentuiThis relates to changes in v1.0, now that opencode uses opentui

   on Jan 21, 2026
4. github-actions commented on Jan 21, 2026

   

   github-actionsBot

   on Jan 21, 2026 – with GitHub Actions

   Contributor

   More 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.
5. KevinWang676 commented on Jan 22, 2026

   

   KevinWang676

   on Jan 22, 2026

   More actions

   ran into the same issue here on my windows machine
6. fdittz commented on Jan 26, 2026

   

   fdittz

   on Jan 26, 2026

   Author

   More actions

   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?
7. github-actions commented on Mar 29, 2026

   

   github-actionsBot

   on Mar 29, 2026 – with GitHub Actions

   Contributor

   More 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.
8. github-actions

   closed this as completedon Mar 29, 2026