# Codex Debugging

> Codex debugging: codex-rs core/tui/exec/cli/app-server/config.

Codex debugging: codex-rs core/tui/exec/cli/app-server/config.

- Page: https://ss33.ai/skills/steipete/codex-debugging-51509748636
- Publisher: steipete
- Category: [Software Development](https://ss33.ai/skills/category/software-development-t44z8z) › [Developer docs & tooling](https://ss33.ai/skills/category/software-development-t44z8z/developer-docs-and-tooling-nich6w)
- License: MIT
- Source: https://github.com/steipete/agent-scripts/blob/6232f9b84bba00bc6594b0443116f58d5654f647/skills/codex-debugging/SKILL.md

## Skill

SKILL.md: https://ss33.ai/api/v1/ss33/download/steipete/codex-debugging-51509748636

# 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:

```bash
cd ~/Projects/codex
sed -n '1,220p' codex-rs/AGENTS.md
```

Then search targeted areas:

```bash
rg "<symbol|setting|error|feature>" codex-rs/{core,tui,exec,cli,app-server,app-server-protocol,config}
```

## Workflow

1. Identify whether the behavior is CLI, TUI, app server, protocol, config, or exec/tooling.
2. Read the owning module and adjacent tests before proposing changes.
3. Check local config in `~/.codex/config.toml` only after understanding the source contract.
4. 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.