opencode-tui-safety

To prevent console pollution in OpenCode TUI plugins, you must eliminate direct console.log usage and replace it with structured logging via the client.app.log() method. This enforces safe, event-driven interaction patterns.

The best way to handle TUI events safely is by interacting with the Terminal UI through safe, event-driven patterns rather than direct UI access. This ensures your plugin maintains rendering performance and reliability.

Your OpenCode TUI plugin drops frames during rendering when it violates 60 FPS performance guardrails. Applying safe plugin development practices and structured logging helps troubleshoot and enforce these reliability standards.

Yes, OpenCode plugin development requires structured logging patterns to avoid visual pollution. You must validate events and route logs through client.app.log() instead of standard console outputs to adhere to safety standards.

You need to audit your code for OpenCode TUI safety when building or modifying terminal UI integrations. This ensures your logging, event handling, and rendering adhere to safety standards and avoid visual pollution.