Plugin output written to TUI as ghost text #1461

Closed
opened 2026-02-16 17:31:04 -05:00 by yindo · 5 comments
Owner

Originally created by @garrett-hopper on GitHub (Aug 23, 2025).

Originally assigned to: @thdxr on GitHub.

I had a typo in a plugin command (using $ for shell command) and was surprised the error was directly written to the TUI message input line. It ended up in a weird broken state due to this (shadow characters which wouldn't go away).

I would expect STDIN/STDERR to be sent in some kind of notification if anywhere instead of written as ghost text in the message input.

Currently adding &>/dev/null to ignore all output to avoid this, though it'd be nice for unexpected output to be surfaced in a nicer way.

Originally created by @garrett-hopper on GitHub (Aug 23, 2025). Originally assigned to: @thdxr on GitHub. I had a typo in a plugin command (using `$` for shell command) and was surprised the error was directly written to the TUI message input line. It ended up in a weird broken state due to this (shadow characters which wouldn't go away). I would expect STDIN/STDERR to be sent in some kind of notification if anywhere instead of written as ghost text in the message input. Currently adding `&>/dev/null` to ignore all output to avoid this, though it'd be nice for unexpected output to be surfaced in a nicer way.
yindo closed this issue 2026-02-16 17:31:04 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Aug 23, 2025):

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

  • #2125: Similar issue where text unexpectedly appears in the input field during scrolling
  • #1864: TUI rendering artifacting issues that cause display problems

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

@github-actions[bot] commented on GitHub (Aug 23, 2025): This issue might be a duplicate of existing issues. Please check: - #2125: Similar issue where text unexpectedly appears in the input field during scrolling - #1864: TUI rendering artifacting issues that cause display problems Feel free to ignore if none of these address your specific case.
Author
Owner

@jensenojs commented on GitHub (Sep 11, 2025):

Image

sth like this?

@jensenojs commented on GitHub (Sep 11, 2025): <img width="791" height="417" alt="Image" src="https://github.com/user-attachments/assets/eda029c9-4db2-4b3f-b839-22881cecb507" /> sth like this?
Author
Owner

@garrett-hopper commented on GitHub (Sep 11, 2025):

That doesn't look like plugin STDIN/STDERR; more just theming issues. Sounds like OpenTUI is likely to fix stuff like that though. (And presumably OP too)

@garrett-hopper commented on GitHub (Sep 11, 2025): That doesn't look like plugin STDIN/STDERR; more just theming issues. Sounds like OpenTUI is likely to fix stuff like that though. (And presumably OP too)
Author
Owner

@outp1 commented on GitHub (Sep 12, 2025):

+1. Not only error outputs breaks TUI and the whole session. When user's input of any kind is required it's also breaks. Like when you asked to enter sudo password.

@outp1 commented on GitHub (Sep 12, 2025): +1. Not only error outputs breaks TUI and the whole session. When user's input of any kind is required it's also breaks. Like when you asked to enter sudo password.
Author
Owner

@rekram1-node commented on GitHub (Dec 27, 2025):

[automated] Closing due to 90+ days of inactivity. Feel free to reopen if you still need this!

@rekram1-node commented on GitHub (Dec 27, 2025): [automated] Closing due to 90+ days of inactivity. Feel free to reopen if you still need this!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#1461