discuss-with-codex

name	discuss-with-codex
description	Use codex/codex-reply as a persistent second-engineer thread for non-trivial uncertainty — design choices, risky implementation decisions, debugging when stuck, review, spec ambiguity, needing a current/authoritative web_search, or any point where you'd otherwise guess. Keep one thread and iterate; don't treat the first answer as gospel.

Codex is a colleague, not an oracle. Use it to test your reasoning.

• Gather local context first. Read the relevant files, diff, spec, logs, or failing output before asking.
• One thread, many turns. Start with codex; continue the same thread with codex-reply + its threadId.
• Send the real artifact. The diff, spec line, stack trace, test output, or concrete options — not a paraphrase.
• State your current read. What you think, what you're unsure of, and the decision you need.
• Push back. Add the missed constraint, challenge assumptions, ask what would change its recommendation.
• Omit the model override. Inherit the configured default; never guess a model id (a stale id errors).