Text renderables pass control characters and ANSI escape sequences from content to the terminal verbatim

Description

Strings containing C0/C1 control characters or ANSI escape sequences (CSI, OSC) that reach text surfaces are written to the terminal verbatim.
The terminal executes them - cursor movement, erase, colour changes, bell, window title changes - and the rendered frames no longer match the terminal state until a full redraw.

Plugins

No response

OpenCode version

opencode2

Steps to reproduce

Render content containing e.g. "before\u001b[2J\u001b[Hafter". The terminal clears/moves the cursor instead of displaying the text. Same with \r, \x07, \u009b, or an OSC sequence like \u001b]0;title\u0007.

Observed in practice through opencode (which renders on @opentui/core + @opentui/solid 0.4.5): a command whose output grepped binary font files produced content with NUL/BEL/BS/CR/ESC bytes (152 ESC sequences, lines up to ~22,000 characters). Rendering it corrupted the whole TUI - overlapping frames, overprinted fragments, stray highlights - until restart.

Screenshot and/or share link

No response

Operating System

Windows 11

Terminal

Windows Terminal