test-tui

Tests the Codex TUI interactively with trace logging and scripted input.

5|1|Updated Jun 26, 2026

Search Tags:#testing #debugging #logging #codex #rust #terminal #tui

One-click install

npx skills add https://github.com/looooonk/better-codex --skill test-tui-looooonk

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: test-tui
Source: https://github.com/looooonk/better-codex/tree/main/.codex/skills/test-tui
Command: npx skills add https://github.com/looooonk/better-codex --skill test-tui-looooonk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Verifying changes to a terminal user interface is difficult without a repeatable way to launch the app, capture detailed logs, and send keystrokes programmatically. This Skill provides a consistent procedure for interactively testing the Codex TUI. ## Core Features & Use Cases - Interactive Launch Procedure: Starts the Codex TUI through the `just codex` target so changes can be verified in a live session. - Trace-Level Logging: Enforces `RUST_LOG="trace"` and a `-c log_dir=<temp_dir>` argument so every run writes detailed logs to a known location for debugging. - Programmatic Input Guidance: Specifies sending text first and Enter in a separate write, avoiding input bursts that the TUI may mishandle. - Use Case: After modifying TUI rendering code, launch the app with trace logging, send a test message programmatically, and inspect the log directory to confirm the change behaves as expected. ## Quick Start Start the Codex TUI with just codex, set RUST_LOG to trace, pass a log directory via -c log_dir, then send a test message followed by Enter as a separate write.

Frequently Asked Questions about test-tui

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

FAQPage Schema

How do I test the Codex TUI interactively?▼

Start the TUI interactively using the just codex target, for example just codex -c log_dir=<temp_dir>. Always set RUST_LOG="trace" before launching so detailed logs are captured for debugging.

How do I capture Codex TUI logs for debugging?▼

Set RUST_LOG="trace" when starting the process and pass -c log_dir=<some_temp_dir> so logs are written to a specific directory. You can then inspect that directory after the session to diagnose issues.

Why does my programmatic test message not submit in the TUI?▼

Sending text and Enter in a single write burst can fail. Send the text first, then send Enter in a separate write so the TUI processes the input correctly.

What command runs the Codex TUI for testing?▼

Use the just codex target to run the TUI, passing configuration overrides such as just codex -c log_dir=<temp_dir>. This ensures the app starts with the expected development setup.