# Codex Debugging

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

- Repository: https://github.com/steipete/agent-scripts (7431 stars)
- Category: Testing
- License: MIT
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add steipete/agent-scripts --skill codex-debugging -g -a claude-code -y`
Codex: `npx skills add steipete/agent-scripts --skill codex-debugging -g -a codex -y`
Cursor: `npx skills add steipete/agent-scripts --skill codex-debugging -g -a cursor -y`
Gemini CLI: `npx skills add steipete/agent-scripts --skill codex-debugging -g -a gemini-cli -y`

## Description

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

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

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