TUI: library console output corrupts alternate screen display

[thomas-bw]

Description

Any console.* output written by library dependencies (Ajv compiling third-party MCP schemas, plugin dependencies, etc.) goes straight to the terminal and lands inside the TUI's alternate screen, corrupting the display with raw warning lines.

#31002 tracks one specific instance (Ajv's unknown format "uint64" ignored), fixed at the source in #48331. This issue tracks the general class of bug: the TUI should be resilient against stray console output from any dependency, not just Ajv.

Plugins

No response

OpenCode version

1.18.30

Steps to reproduce

1. Configure an MCP server whose tool schemas contain non-standard format values like uint32/uint64 (e.g. Rust/schemars)
2. Start opencode (TUI)
3. Ajv warnings appear as raw lines overwriting the TUI display

Screenshot and/or share link

Operating System

Ubuntu 24

Terminal

Bash

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• TUI is overwritten by raw plugin or worker output #43064: "TUI is overwritten by raw plugin or worker output" — very similar: raw stdout/stderr writes from in-process plugins corrupt the TUI alternate screen display
• Background hook stderr output can be painted into the input box until terminal repaint #31219: "Background hook stderr output can be painted into the input box" — same root symptom of unguarded terminal writes corrupting the TUI frame
• v18 tui is broken (console logs broke everything) #37455: "v18 tui is broken (console logs broke everything)" — console output breaking the TUI display

If your issue is distinct from these (e.g. the general-class tracking angle you describe vs. a specific instance), please add a note clarifying how it differs so maintainers can keep them appropriately linked.

[thomas-bw]

This issue is distinct from all three. It intentionally tracks the general class of "any console.* output from library dependencies corrupts the TUI's alternate screen", not a specific instance:

• v18 tui is broken (console logs broke everything) #37455 and MCP schema warnings: non-standard "format" values (uint32/uint64) from schemars pollute TUI #31002 are concrete instances of this class (a user plugin's console.log, Ajv's unknown format "uint64" warning). MCP schema warnings: non-standard "format" values (uint32/uint64) from schemars pollute TUI #31002 was already fixed at the source in fix(mcp): silence Ajv unknown format warnings from MCP tool schemas #48331 (Ajv logger disabled via the MCP SDK's ClientOptions); TUI: library console output corrupts alternate screen display #48520 exists so the TUI is resilient against the next library that emits console output, whichever it is.
• TUI is overwritten by raw plugin or worker output #43064 is the complementary case, not the same one: it concerns raw process.stdout/stderr.write from in-process plugins/workers and --print-logs output, and explicitly notes that console.* is captured there. This issue covers only the console.* path. TUI is overwritten by raw plugin or worker output #43064 should stay open to track the raw-stdio half of the problem.
• Background hook stderr output can be painted into the input box until terminal repaint #31219 is a different symptom detail: background hook stderr painted into the input box until the next repaint (cursor-placement/repaint behavior), not console output corrupting the alternate screen.

This issue is already linked to its fix: #48517 installs a ConsoleGuard in every TUI entrypoint (tui, attach, run) and the server worker, redirecting console.debug/info/log/warn/error into the opencode log file while respecting OPENCODE_LOG_LEVEL. Non-TUI entrypoints keep normal console behavior.