codex - 💡(How to fix) Fix /goal` mode repeatedly emits dangerous-operation confirmation prompt and consumes quota

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
RAW_BUFFERClick to expand / collapse

What version of Codex CLI is running?

codex-cli 0.130.0

What subscription do you have?

20x

Which model were you using?

/goal gpt-5.5-codex

What platform is your computer?

No response

What terminal emulator and version are you using (if applicable)?

No response

What issue are you seeing?

When using /goal mode, a task triggered the dangerous-operation confirmation rules from AGENTS.md.

The agent correctly detected that the task involved deleting files and asked for explicit confirmation, but it did not pause while waiting for the user response. Instead, it repeatedly emitted the same dangerous-operation confirmation prompt and kept consuming quota.

The repeated prompt was essentially:

  • Dangerous operation detected
  • Operation type: delete files
  • Scope: 21 non-integration test files under the course service directory
  • Please confirm whether to continue: “yes”, “confirm”, or “continue”

After that, it repeatedly stated that confirmation was still missing, so it could not delete the files and could not mark the goal complete.

Expected behavior: once confirmation is required, /goal should stop and wait for the user. It should not keep regenerating the same prompt or consume additional quota while blocked on confirmation.

What steps can reproduce the bug?

  1. Create or use a project with an AGENTS.md file that requires explicit confirmation for dangerous operations such as deleting files.
  2. Start a task using /goal.
  3. Ask the agent to perform a task that includes deleting multiple files.
  4. Let the agent detect the dangerous operation and ask for explicit confirmation.
Dangerous operations require explicit confirmation before proceeding.
Deleting files is considered dangerous.
Actual result: /goal repeatedly emits the confirmation prompt and consumes quota.

Expected result: /goal enters a blocked/waiting-for-user-confirmation state after the first prompt.

### What is the expected behavior?

_No response_

### Additional information

_No response_

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix /goal` mode repeatedly emits dangerous-operation confirmation prompt and consumes quota