Ctrl+C during response causes terminal to print endless garbage and become unresponsive #10265

Description

When using opencode in the terminal, if I accidentally press Ctrl+C while a response is still being streamed from the model, the opencode interface exits, but the terminal starts dumping continuous garbage output (usually mangled tokens / partial ANSI sequences / binary-like data).

Once this starts:

• Further Ctrl+C, Ctrl+D, ESC, q, etc. have no effect
• The terminal keeps spamming output indefinitely
• The only way to stop it is to force-close the terminal tab/window or kill the process externally

Plugins

No response

OpenCode version

1.1.34

Steps to reproduce

1. Open opencode in your terminal
2. Send a request that produces a reasonably long / slow response
3. While the response is actively streaming (not yet finished), press Ctrl+C

Screenshot and/or share link

Operating System

windows 11

Terminal

powershell