[Bug] TUI fails to render with raw ANSI output and critical memory leak (72.5G VIRT) on startup

[roymecat]

Description

I am trying to run opencode on my Debian 13.1. The tool fails to launch the TUI properly. Instead of showing the interface, it floods the terminal with raw ANSI escape sequences (specifically mouse reporting codes like ^[[<35;84;4M).

Crucially, I observed via htop that the process immediately consumed an abnormal amount of memory: 71.9G of VIRT. This suggests a massive memory leak or an infinite allocation loop during the initialization phase.

OpenCode version

latest version

Steps to reproduce

Environment: Debian 13.1(Headless, connected via SSH).
Run the command opencode in a project directory.
The terminal output becomes corrupted with raw escape codes.
Check process status in htop.

Screenshot and/or share link

Operating System

Debian 13.1

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
• OpenCode TUI Hangs on Fedora Linux (npm & bun & standalone) #6080: OpenCode TUI Hangs on Fedora Linux (npm & bun & standalone)
• Nothing is displayed #6057: Nothing is displayed

These issues report similar symptoms of TUI rendering failures, ANSI escape sequence corruption, and memory/hanging issues on Linux systems. Feel free to ignore if your specific case differs from these.