/goal` mode repeatedly emits dangerous-operation confirmation prompt and consumes quota

Resolved 💬 5 comments Opened May 12, 2026 by wantMeat Closed May 30, 2026

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.

  1. Start a task using /goal.
  2. Ask the agent to perform a task that includes deleting multiple files.
  3. Let the agent detect the dangerous operation and ask for explicit confirmation.

```text
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_

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗