Terminal output becomes garbled after running for a while and also when pressing Ctrl+C

[RaymondGuoCGI]

Description

The terminal output becomes garbled in two different situations:

1. After Opencode has been running for a period of time, even without any interruption
2. When pressing Ctrl+C to interrupt the process

In both cases, the terminal starts printing raw ANSI escape sequences, and the screen becomes unreadable.

Steps to reproduce

Case 1: After running for a while

1. Run Opencode in a Windows terminal
2. Let it run for some time during normal operation
3. Observe that the terminal output gradually becomes garbled

Case 2: After pressing Ctrl+C

1. Run Opencode in a Windows terminal
2. Press Ctrl+C while it is running
3. Observe that the terminal output immediately becomes garbled

Expected behavior

The terminal output should remain readable during long-running sessions,
and the terminal state should be properly restored after Ctrl+C.

Actual behavior

The terminal enters a corrupted state and continues printing raw ANSI escape codes.

Environment

• OS: Windows
• Terminal: Windows Terminal (or cmd / PowerShell)
• Opencode version: (please fill in)
• Model / Agent: GPT-5.3 Codex / Sisyphus

Additional notes

This appears to be related to terminal state management.
The terminal may be left in raw mode or not properly reset,
both during long-running execution and after handling SIGINT.

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

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:

• Terminal output becomes garbled after running for a while and also when pressing Ctrl+C #12663: Terminal output becomes garbled after running for a while and also when pressing Ctrl+C (closed)
• 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)
• Bug: Ctrl+C causes terminal UI rendering overlap on Windows Terminal (v1.1.16) #8159: Bug: Ctrl+C causes terminal UI rendering overlap on Windows Terminal (v1.1.16)
• Terminal state not restored when exiting with ctrl+c on windows (git bash) #10719: Terminal state not restored when exiting with ctrl+c on windows (git bash)
• macOS: Terminal becomes unusable after opencode exits ("dead terminal") #7861: macOS: Terminal becomes unusable after opencode exits ("dead terminal")
• Ctrl+C during response causes terminal to print endless garbage and become unresponsive #10265: Ctrl+C during response causes terminal to print endless garbage and become unresponsive
• Input sometimes starts to only show ASCII escape codes #5181: Input sometimes starts to only show ASCII escape codes
• 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
• OpenCode Crashes then outputs garbled tokens - ;5M[555;27;47M[555 #10783: OpenCode Crashes then outputs garbled tokens
• After closing the OpenCode CLI, scrolling the mouse wheel and moving the mouse in the powershell will cause garbled characters. #11748: After closing the OpenCode CLI, scrolling the mouse wheel and moving the mouse in the powershell will cause garbled characters

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

[Hona]

ctrl+c handling is now in as of 1.1.60