Codex Debugging
Codex debugging: codex-rs core/tui/exec/cli/app-server/config.
by steipete · MIT
The skill
Codex debugging: codex-rs core/tui/exec/cli/app-server/config.
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}
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.
Use this skill
Connect your agent to the Skill Store MCP server and ask for it by ref: steipete/codex-debugging-51509748636.
Details
- Publisher
- steipete
- Category
- Software Development › Developer docs & tooling
- License
- MIT
- Updated
- 2026-10-18
References
More from steipete
- Agent Transcript Requested GitHub PR/issue agent transcripts: redact, trim, preview, and insert safely.
- Beeper Beeper cache: contact hints, room lookup, WhatsApp/iMessage traces, FTS.
- Browser Use Control the user's existing signed-in Chrome: callable Codex Chrome plugin first, then OpenClaw e…
- Clawsweeper Status ClawSweeper status: URLs, workflow health, active workers, ops snapshot.