Input field disappears and error data is shown in the background while waiting for model response #7606

Open
opened 2026-02-16 18:07:42 -05:00 by yindo · 3 comments
Owner

Originally created by @ghtndl on GitHub (Jan 26, 2026).

Originally assigned to: @kommander on GitHub.

Description

When submitting a prompt to a model in the OpenCode TUI, the input field disappears while waiting for the model response.

During this waiting period, raw error-related data is rendered in the background instead of a stable loading or input state.

This appears to be unintended behavior and results in a confusing user experience.

Plugins

oh-my-opencode

OpenCode version

1.1.36

Steps to reproduce

  1. Run OpenCode in TUI mode on Windows using Windows Terminal (windowed mode).
  2. Submit a prompt to a model.
  3. While waiting for the model response, observe that the input field disappears and error-related data is rendered in the background.
  4. Resize the terminal to fullscreen mode.
  5. Switch back from fullscreen to windowed mode.
  6. Observe that the background UI returns to its normal state.

Screenshot and/or share link

Image Image Image

Operating System

windows11

Terminal

windows terminal

Originally created by @ghtndl on GitHub (Jan 26, 2026). Originally assigned to: @kommander on GitHub. ### Description When submitting a prompt to a model in the OpenCode TUI, the input field disappears while waiting for the model response. During this waiting period, raw error-related data is rendered in the background instead of a stable loading or input state. This appears to be unintended behavior and results in a confusing user experience. ### Plugins oh-my-opencode ### OpenCode version 1.1.36 ### Steps to reproduce 1. Run OpenCode in TUI mode on Windows using Windows Terminal (windowed mode). 2. Submit a prompt to a model. 3. While waiting for the model response, observe that the input field disappears and error-related data is rendered in the background. 4. Resize the terminal to fullscreen mode. 5. Switch back from fullscreen to windowed mode. 6. Observe that the background UI returns to its normal state. ### Screenshot and/or share link <img width="2222" height="1021" alt="Image" src="https://github.com/user-attachments/assets/348f4e88-8f12-4c90-aa7a-5cb21152cc62" /> <img width="1285" height="341" alt="Image" src="https://github.com/user-attachments/assets/ab24afeb-0a43-4e91-8d20-4632c7fc182a" /> <img width="2218" height="1174" alt="Image" src="https://github.com/user-attachments/assets/1666fac4-197a-4b32-a28c-5d3d31980311" /> ### Operating System windows11 ### Terminal windows terminal
yindo added the windowsopentuibug labels 2026-02-16 18:07:42 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 26, 2026):

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

  • #9798: The Windows Terminal interface is not displaying correctly after answering a question (similar display corruption on Windows Terminal)
  • #8639: Background logs are printed to the TUI (background data being rendered instead of proper UI state, fixed by window resize)
  • #6749: The tui in the input line disappeared (input field disappearing issue)

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

@github-actions[bot] commented on GitHub (Jan 26, 2026): This issue might be a duplicate of existing issues. Please check: - #9798: The Windows Terminal interface is not displaying correctly after answering a question (similar display corruption on Windows Terminal) - #8639: Background logs are printed to the TUI (background data being rendered instead of proper UI state, fixed by window resize) - #6749: The tui in the input line disappeared (input field disappearing issue) Feel free to ignore if none of these address your specific case.
Author
Owner

@kommander commented on GitHub (Jan 26, 2026):

Please try without any plugins. Does it still happen?

@kommander commented on GitHub (Jan 26, 2026): Please try without any plugins. Does it still happen?
Author
Owner

@ghtndl commented on GitHub (Jan 26, 2026):

I’m no longer able to reproduce the issue when running OpenCode without the plugin.
This suggests that the issue may be related to the plugin rather than OpenCode itself.

Thank you for your efforts.

@ghtndl commented on GitHub (Jan 26, 2026): I’m no longer able to reproduce the issue when running OpenCode without the plugin. This suggests that the issue may be related to the plugin rather than OpenCode itself. Thank you for your efforts.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#7606