[Windows] Raw ANSI escape codes flooding console & "Unable to connect" errors during tool execution (v1.1.36) #10945

Description

I am encountering two critical issues when running OpenCode on Windows using an internal/custom LLM endpoint.
Console Flooding: The terminal output is flooded with raw ANSI escape codes (e.g., [38;2;..., [0m), making the interface unreadable. This appears to be raw token streaming mixed with unparsed color codes.
Tool Execution Failure: When the model attempts to call tools (e.g., glob), it fails with connection errors, possibly indicating that the agent runtime/sidecar process is unreachable or crashed.

Additional Context
I am running this in a corporate intranet environment.
No proxy environment variables (HTTP_PROXY, etc.) are actively blocking localhost, but the error suggests a local networking/IPC failure between the UI and the tool execution service.
Hypothesis: The excessive stdout flooding might be blocking the IPC pipe, or the backend process responsible for tool execution is crashing silently (or failing to start) due to the Windows environment configuration.

Plugins

No response

OpenCode version

v1.1.36

Steps to reproduce

1.Launch: Run opencode in PowerShell.
2.Initial State: The TUI loads correctly. The layout, font colors, and interactive elements are displayed normally without any issues.
3.Interaction: Send a prompt that triggers a complex response or tool use (e.g., analyzing codebase).
4.The Crash: After running for a short while (during the streaming response), the UI layout suddenly breaks.
The screen starts printing raw content mixed with ANSI codes (e.g., [38;2;...) continuously.
The output scrolls infinitely and uncontrollable.
5.Termination: The session becomes unresponsive to normal commands, requiring a Ctrl+C to forcibly kill the process.

Screenshot and/or share link

No response

Operating System

windows10

Terminal

Windows powershell