codex-log-readerlisted

# Codex Log Reader Bundled commands use `$PLUGIN_ROOT` (`$env:PLUGIN_ROOT` in PowerShell; same path suffix) for the plugin root. Set it once: use the host's plugin-root variable when defined (Claude Code: `PLUGIN_ROOT="$CLAUDE_PLUGIN_ROOT"`), otherwise the absolute path of this plugin's root directory. Use this skill to find the smallest useful slice of Codex logs before opening raw JSONL. Session logs are useful evidence, but they can contain user prompts, tool I/O, environment fragments, URLs, and secrets. If the question spans the newest `N` tasks, repeated behavior across sessions, or a capability-gap corpus, use `codex-task-corpus` instead of repeatedly running single-rollout searches. Return here only for bounded per-task evidence. For deeper log locations, JSONL shape, manual `jq` fallbacks, and safety rules, read `$PLUGIN_ROOT/references/log-reader-safety.md`. ## Fast Path Primary tool: ```bash python3 "$PLUGIN_ROOT/scripts/codex_log_reader.py" --help ``` Decision tree: 1. If the user provides `CODEX_THREAD_ID`, locate exactly: ```bash python3 "$PLUGIN_ROOT/scripts/codex_log_reader.py" find --thread-id <thread-id> ``` Once exact lookup succeeds, do not broaden to filesystem search, SQLite, or raw JSONL unless a specific missing fact requires it. 2. If the user gives a project path, issue key, app name, or vague "find that run", rank likely sessions: ```bash python3 "$PLUGIN_ROOT/scripts/codex_log_reader.py" find --cwd /path/to/project