What problem does it solve? Verifying changes to the Codex terminal UI requires manually launching the app, typing messages, and hunting for logs, which is slow and error-prone. This Skill provides a repeatable procedure for starting the TUI interactively, capturing trace-level logs, and sending test input programmatically. ## Core Features & Use Cases - Interactive TUI Launch: Start Codex TUI via the just codex target with trace-level logging enabled through RUST_LOG. - Log Capture to a Directory: Pass -c log_dir=<temp_dir> so logs are written to a known location for debugging. - Programmatic Input: Send test messages by writing text first and Enter as a separate write, avoiding input races. - Use Case: After modifying TUI rendering code, launch the app with trace logging, send a scripted message, and inspect the log directory to confirm the new behavior. ## Quick Start Start Codex TUI interactively with RUST_LOG=trace and a log directory, then send a test message followed by a separate Enter keystroke to verify my changes.