Codex 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}

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.toml only after understanding the source contract.
Prefer small repros or focused tests over broad speculation.

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.

Use when investigating Codex CLI/app behavior, config parsing, tool behavior, prompts, MCP/app wiring, or runtime bugs.

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}

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.toml only after understanding the source contract.
Prefer small repros or focused tests over broad speculation.

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.