About codex-debugging
codex-debugging is a skill for investigating Codex CLI and app behavior, configuration, tools, prompts, MCP wiring, and runtime bugs. It guides analysis from the relevant local source and tests, with focused reproductions preferred over speculation.
Key features
- 01Classifies issues by Codex component
- 02Inspects relevant source modules and tests
- 03Checks local configuration against source behavior
- 04Uses focused reproductions or tests
- 05Consults official docs when source is insufficient
Use cases
- 01Investigating Codex CLI or app behavior
- 02Tracing configuration parsing or tool issues
- 03Debugging prompts and MCP or app wiring
- 04Reproducing runtime bugs before proposing changes
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ steipete/ agent-scripts --skill codex-debuggingAfter installing, type/codex-debuggingin Claude Code to confirm it loaded.
Details
From the project READMECodex Debugging
Use when investigating Codex CLI/app behavior, config parsing, tool behavior, prompts, MCP/app wiring, or runtime bugs.
Source First
Prefer local source before web/docs:
cd ~/Projects/codex
sed -n '1,220p' codex-rs/AGENTS.md
Then search targeted areas:
rg "<symbol|setting|error|feature>" codex-rs/{core,tui,exec,cli,app-server,app-server-protocol,config}
Workflow
- Identify whether the behavior is CLI, TUI, app server, protocol, config, or exec/tooling.
- Read the owning module and adjacent tests before proposing changes.
- Check local config in
~/.codex/config.tomlonly after understanding the source contract. - Prefer small repros or focused tests over broad speculation.
Notes
- For OpenAI API/product docs, use the official-docs path only when source is insufficient.
- For local browser automation in CLI, use
$browser-use; the bundled Browser plugin is Codex app-only.
Comments
Markdown supported