Repository navigation
Conversation
|
Confirming this fix is needed: Windows 11 + Orca IDE (xterm.js-based terminal) + opencode 1.18.18 — stale-width artifacts appear on every session completion (leftover frames, garbled panels), recoverable only by forcing a grow-resize (changing tab zoom) or restarting opencode. Tested and ruled out: switching the terminal to DOM renderer (Orca "GPU Acceleration" → Off) does NOT fix it — the issue is the TUI resize handling, not the renderer. Please land this. |
|
Automated PR Cleanup Thank you for contributing to opencode. Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions. This PR was closed because it matched the following cleanup criteria:
PRs created within the last month are not affected by this cleanup. If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate. Thanks again for taking the time to contribute. |
Issue for this PR
Closes #42225
Type of change
What does this PR do?
OpenTUI reads
process.stdout.columnsandprocess.stdout.rowswhen handlingSIGWINCH. In affected PTY hosts, Bun can leave those cached values stale until the stream refreshes its window size.This change refreshes the TTY dimensions before OpenTUI receives the resize signal. It performs one initial refresh, installs the listener ahead of the renderer listener, and removes it when the TUI scope closes.
How did you verify your code works?
bun testinpackages/tui: 195 passed, 1 skippedbun typecheckinpackages/tuiScreenshots / recordings
Not included. The failure is specific to live terminal resizing; the signal ordering is covered by a focused regression test and was also verified interactively in tmux.
Checklist