Skip to content

Conversation

@noah79
Copy link

@noah79 noah79 commented Dec 31, 2025

Summary

  • Remove 4 debug console.log statements that write to stdout and corrupt TUI rendering
  • Fixes visual artifacts including text bleeding, HTML entities (>) appearing, and model picker content corrupting the main view

Changes

File Removed
app.tsx:199 console.log(JSON.stringify(route.data))
route.tsx:34 console.log("navigate", route)
dialog-session-list.tsx:61 console.log("session count", ...)
prompt/index.tsx:606 console.log(command)

Root Cause

In terminal UI applications, console.log writes to stdout which interferes with the terminal rendering. These debug statements were left in from development and cause visual corruption when triggered during normal TUI operation.

Testing

  • Verified TUI renders correctly after removal
  • Typecheck passes

Remove leftover debug logging that writes to stdout and corrupts TUI rendering:
- app.tsx: Remove route.data JSON logging
- route.tsx: Remove navigate logging
- dialog-session-list.tsx: Remove session count logging
- prompt/index.tsx: Remove command logging

These console.log statements write to stdout which interferes with the
terminal UI rendering, causing text bleeding and visual artifacts.
@rekram1-node
Copy link
Collaborator

rekram1-node commented Dec 31, 2025

I thought opentui automatically captures these and puts them in the debug console.

Are these issues you noticed and fixed yourself or did you have an llm make these changes without specific prompting to fix.

…tion

Remove disableStdoutInterception() call that was preventing opentui from
intercepting stdout writes. This allows the TUI framework to capture any
stdout output (from subprocesses, hooks, or external processes) that would
otherwise corrupt the terminal display.
@github-actions github-actions bot mentioned this pull request Jan 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants