TUI does not fully repaint after Ctrl+Z + fg when terminal is resized

[Piping]

Description

When OpenCode TUI is suspended with Ctrl+Z, the terminal is resized, and then resumed with fg, the UI may return in a partially stale state (misaligned characters / incomplete redraw).

Plugins

No response

OpenCode version

v1.2.20 (reproduced on current dev before fix)

Steps to reproduce

1. Launch opencode in terminal (TUI mode).
2. Press Ctrl+Z to suspend the process.
3. Resize the terminal window while in shell.
4. Run fg to resume opencode.
5. Observe the restored screen.

Screenshot and/or share link

No response

Operating System

macOS

Terminal

Reproduced in local terminal session (reporter environment)

Expected behavior

After fg, TUI should fully repaint using current terminal dimensions.

Actual behavior

After fg, parts of the old frame can remain and rendering is not fully refreshed.

Related PR

• fix(tui): refresh screen correctly after Ctrl+Z resume #16326

[github-actions]

This issue doesn't fully meet our contributing guidelines.

What needs to be fixed:

• The Description field just repeats the issue title rather than providing actual details about the bug
• Steps to reproduce are missing — please describe how to trigger this behavior
• OpenCode version, Operating System, and Terminal fields are all empty — this context is important for diagnosing the issue

Please edit this issue to address the above within 2 hours, or it will be automatically closed.

---

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

• Suspend (ctrl + z) pauses api calls for all opencode instances #5043: Suspend (ctrl+z) pauses API calls for all opencode instances — also involves ctrl+z / fg behavior

If you believe this was flagged incorrectly, please let a maintainer know.

[github-actions]

Thank you for updating the issue! It now meets our contributing guidelines — the description, reproduction steps, and system info all look good. We appreciate you taking the time to fill things in properly.

[N-R-K]

Ran into this on linux as well. Using v1.4.0. Very annoying bug, would appreciate if a fix is merged soon.