PluginBench
Skill
Official
Review
Audit score 70

test-tui

openai/codex

Interactive testing guide for Codex TUI with debugging support.

What is test-tui?

Guide for starting and testing the Codex TUI interactively. Use this to verify changes and debug issues by running the TUI with trace logging and custom log directories.

  • Start Codex TUI interactively for manual testing
  • Enable trace-level logging with RUST_LOG environment variable
  • Write logs to a custom directory for debugging
  • Send test messages programmatically with proper sequencing
  • Run via the just codex target with custom arguments

How to install test-tui

npx skills add https://github.com/openai/codex --skill test-tui
Prerequisites
  • Codex repository cloned locally
  • just task runner installed
  • Rust environment configured
Claude Code
Cursor
Windsurf
Cline

How to use test-tui

  1. 1.Set RUST_LOG=trace environment variable
  2. 2.Run just codex -c log_dir=<temp_directory> to start with logging
  3. 3.Interact with the TUI manually to test features
  4. 4.When sending test messages programmatically, send text first, then send Enter separately
  5. 5.Check the log directory for trace output to debug issues

Use cases

Good for
  • Verify TUI changes before committing
  • Debug TUI behavior with detailed trace logs
  • Test message handling and input processing
  • Troubleshoot interactive features in isolation
  • Capture logs to a temporary directory for analysis
Who it's for
  • Codex developers
  • QA engineers testing TUI functionality
  • Contributors debugging interactive features

test-tui FAQ

Why should I send text and Enter separately?

Sending text and Enter in one burst can cause issues with message processing. Send the text first, then send Enter in a separate write operation.

How do I capture logs for debugging?

Pass the -c log_dir=<some_temp_dir> argument when running just codex to write logs to a specific directory.

What logging level should I use?

Always set RUST_LOG=trace when starting the process to get detailed trace-level logging for debugging.

What command should I use to run the TUI?

Use the just codex target, optionally with arguments like -c log_dir=<temp_dir>.

Full instructions (SKILL.md)

Source of truth, from openai/codex.


name: test-tui description: Guide for testing Codex TUI interactively

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 ...