codex - 💡(How to fix) Fix When asked to file a GitHub issue from user feedback, Codex drafts it from repo artifacts instead [1 comments, 2 participants]

What happened

In an interactive Codex terminal session, I first told Codex to handle the commit itself. After some back-and-forth, I changed the task and explicitly told it to submit a GitHub issue itself.

At that point, Codex did not treat my feedback in the conversation as the primary source for the issue. Instead, it started reading local repo docs and code artifacts to synthesize the issue content. I had to correct it again and say that the issue should be based on my feedback, not on my repository files.

Why this is a bug

Once the user switches from repo work to product feedback filing, the conversation feedback should become the primary source of truth. Repo context is secondary and should not override the user's explicit instruction.

Reproduction

1. Start a Codex terminal session inside a repository with local context available.
2. Ask Codex to handle a task directly (for example, commit changes itself).
3. Interrupt and explicitly redirect it to "submit the issue to GitHub yourself."
4. Observe that Codex starts mining local docs/code to draft the issue instead of drafting it from the user's feedback in the conversation.
5. Correct it again with something equivalent to "not based on my docs and code, but based on my feedback."

Actual behavior

• Codex over-indexes on repository context even after the user changes the task to feedback filing.
• The agent needs repeated user intervention to stop using local docs/code as the issue source.
• The interaction becomes longer and more manual than necessary.

Expected behavior

• When the user explicitly asks Codex to file a GitHub issue based on feedback, Codex should draft the issue from the conversation feedback first.
• Repo files should only be used if the user explicitly asks for repo-based evidence or supporting material.
• If anything is ambiguous, the only question should be the narrow missing detail (for example, target repo), not a reset back into repo analysis.

Environment

• Codex terminal agent
• Windows / PowerShell
• Repository/worktree context present, but the bug is about instruction prioritization and issue drafting behavior

Additional note

A related usability problem is that explicit "do it yourself" style instructions can still degrade into extra approval/context churn before Codex recognizes the user's intent shift.