macOS: Terminal becomes unusable after opencode exits ("dead terminal")

[RandyMcMillan]

Description

When running opencode on macOS and exiting (Ctrl+C, closing terminal, or normal exit), the terminal is left in an unusable state with scrambled output, requiring users to manually reset it with reset command or reopen terminal.

Expected Behavior:
Terminal should be restored to a usable state when opencode exits.

Actual Behavior:
Terminal is left in a corrupted state with:

• Scrambled text output
• Unresponsive input
• Cursor positioning issues
• Requires manual reset command
  Environment
• OS: macOS (any version)
• Terminal: Terminal.app, iTerm2, ...
• opencode version: [current]
  Additional Context
  This appears to be related to terminal escape sequences and alternate screen buffer management not being properly cleaned up on exit.

Plugins

No response

OpenCode version

No response

Steps to reproduce

1. Run opencode on macOS (Terminal.app, iTerm2, ...)
2. Use the application normally
3. Exit opencode using Ctrl+C or normal exit
4. Terminal becomes corrupted/unresponsive

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

[github-actions]

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

• Bug: Ctrl+C interruption in opencode causes terminal corruption with ANSI escape sequences #5990: Bug: Ctrl+C interruption in opencode causes terminal corruption with ANSI escape sequences (Windows)
• Ctrl+C does not disable mouse tracking, causing raw escape sequences to flood terminal (Windows) #6912: Ctrl+C does not disable mouse tracking, causing raw escape sequences to flood terminal (Windows)
• Pressing Ctrl+C in input field outputs ANSI escape sequences/garbled text #7062: Pressing Ctrl+C in input field outputs ANSI escape sequences/garbled text

These issues describe very similar terminal corruption/scrambling when exiting opencode. While those focus on Windows and specific Ctrl+C handling, they may share the same root cause related to terminal escape sequence cleanup on exit.

Feel free to ignore if your case is specifically different from these.

[RandyMcMillan]

#7861 (comment)

https://github.com/anomalyco/opencode/pull/7860/files#r2680287550

[kommander]

Is that happening when exiting with ctrl+c from the error boundary screen or just always? This only has been an issue on windows so far.

[RandyMcMillan]

I will attempt to do a deeper investigation into open-tui. Maybe the appropriate fix needs to be there.

I am not setup to debug in Windows.