Test Tui
Manually exercise the Codex TUI after changes using trace logs, a dedicated log_dir, and correct Enter sequencing for automated input.
Overview
Test TUI is an agent skill for the Ship phase that guides interactive Codex terminal UI verification with trace logging and correct programmatic input timing.
Install
npx skills add https://github.com/openai/codex --skill test-tuiWhat is this skill?
- Start Codex TUI interactively rather than assuming headless pass/fail
- Always set RUST_LOG=trace when launching for deep diagnostics
- Pass -c log_dir=<temp_dir> to capture logs for debugging failures
- Send test input as text first, then Enter in a separate write—not one burst
- Use just codex target: just codex -c ... for repo-aligned runs
- Requires RUST_LOG="trace" for diagnostic runs
- Two-step input rule: text write then separate Enter write
Adoption & trust: 1.2k installs on skills.sh; 89.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You merged TUI changes but lack a consistent way to launch Codex, capture trace logs, and send keystrokes without flaky combined Enter writes.
Who is it for?
Codex repo contributors validating TUI behavior locally after Rust or UX edits.
Skip if: Pure unit-test authoring unrelated to the Codex TUI or production deployment runbooks.
When should I use this skill?
You need to guide interactive testing of Codex TUI to verify changes (per skill description).
What do I get? / Deliverables
You run an instrumented interactive TUI session with logs on disk and reproducible input steps suitable for debugging regressions.
- Trace-enabled interactive TUI session
- Log bundle under configured log_dir
- Documented input sequence for automated prompt tests
Recommended Skills
Journey fit
Testing is the canonical shelf because the skill documents interactive verification of the Codex terminal UI—not feature implementation. TUI regression checks belong in ship when you validate CLI/agent UX before merging or releasing Codex changes.
How it compares
Interactive TUI smoke guide—not a replacement for automated integration test suites or generic Rust cargo test workflows.
Common Questions / FAQ
Who is test-tui for?
Developers shipping changes to Codex’s terminal UI who need a short, repo-native checklist for manual verification.
When should I use test-tui?
During ship/testing before merging TUI fixes, when debugging trace-level session issues, or when automating scripted input against the TUI.
Is test-tui safe to install?
It is procedural documentation; confirm trust via the Security Audits panel on this page and only run just codex from sources you control.
SKILL.md
READMESKILL.md - Test Tui
You can start and use Codex TUI to verify changes. Important notes: Start interactively. Always set RUST_LOG="trace" when starting the process. Pass `-c log_dir=<some_temp_dir>` argument to have logs written to a specific directory to help with debugging. When sending a test message programmatically, send text first, then send Enter in a separate write (do not send text + Enter in one burst). Use `just codex` target to run - `just codex -c ...`