test-tui

Test Codex TUI interactively with trace logging and scripted input.

Updated Aug 4, 2026
One-click install
npx skills add https://github.com/sjc786526-coder/RONDO --skill test-tui-sjc786526-coder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-tui
Source: https://github.com/sjc786526-coder/RONDO/tree/main/multidev/.codex/skills/test-tui
Command: npx skills add https://github.com/sjc786526-coder/RONDO --skill test-tui-sjc786526-coder

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about test-tui

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test Codex TUI changes interactively?▼

Start the TUI with the just codex target, set RUST_LOG=trace, and pass -c log_dir=<temp_dir> so logs are written to a known directory. Then interact with the UI or send scripted input to verify your changes.

How do I send a test message to a terminal UI programmatically?▼

Send the message text first, then send Enter in a separate write operation. Sending text and Enter together in one burst can cause input handling problems in the TUI.

How do I enable trace logging for a Rust TUI application?▼

Set the RUST_LOG environment variable to trace when starting the process. Combine this with the -c log_dir argument so the trace output is written to a specific directory for later inspection.

Where do Codex TUI debug logs get written?▼

Logs are written to the directory you specify with the -c log_dir=<some_temp_dir> argument at startup. Point it at a temporary directory to keep debug output isolated and easy to inspect.

Why does scripted input fail when testing a terminal UI?▼

A common cause is sending text and the Enter key in a single write burst, which the TUI may not process correctly. Split the input into a text write followed by a separate Enter write.