Codex CLI exposes raw <proposed_plan> tags in non-plan mode instead of triggering the plan confirmation flow

What version of Codex CLI is running?

0.142.4

What subscription do you have?

ChatGPT Plus

Which model were you using?

gpt-5.5

What platform is your computer?

Microsoft Windows NT 10.0.19045.0 x64

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

Windows Terminal

Codex doctor report

What issue are you seeing?

Summary

When using Codex CLI in non-plan mode, discussing implementation approaches may cause the model to output a <proposed_plan>...</proposed_plan> block directly in the terminal.

Instead of exposing the raw markup, I expected the CLI to recognize it and enter the normal plan confirmation flow, allowing me to review and approve the proposed plan before proceeding.

Steps to reproduce

1. Launch Codex CLI without enabling plan mode.
2. Ask the model to discuss implementation options or propose an approach before making any changes.
3. Wait for the model to produce a proposed plan.
4. Observe that the terminal displays a raw <proposed_plan>...</proposed_plan> block.

Expected behavior

If the model generates a proposed plan, the CLI should:

• Detect the proposed plan.
• Automatically transition into the plan confirmation workflow.
• Present the plan in a user-friendly format.
• Wait for user confirmation before continuing.

Alternatively, if plan mode is intentionally disabled, the internal <proposed_plan> markup should never be exposed directly to the user.

Actual behavior

The CLI prints the raw <proposed_plan> and </proposed_plan> tags as part of the model output.

The plan is not interpreted by the CLI, and the normal confirmation workflow is not triggered.

Why this seems incorrect

The <proposed_plan> block appears to be an internal protocol or structured output intended for the CLI to consume. Exposing these tags directly suggests that the output is not being parsed correctly or that the CLI is missing the logic to transition into the plan confirmation flow in this scenario.

Environment

• Codex CLI version: (please fill in)
• Operating System: (please fill in)
• Shell: (please fill in)
• Model: (please fill in, if applicable)

Additional context

This issue seems to occur specifically when not using plan mode. The model still emits a proposed plan, but the CLI treats it as plain text instead of invoking the corresponding user interaction.

What steps can reproduce the bug?

1. Start a Codex CLI session without enabling plan mode.

1. Ask Codex to discuss or compare implementation approaches before making any file changes.

Example prompt:

“Before editing any files, please discuss the possible implementation approaches and recommend one.”

1. Wait for Codex to respond with a proposed approach.

1. Observe that the CLI prints a raw <proposed_plan>...</proposed_plan> block directly in the terminal.

1. The CLI does not automatically enter the plan confirmation flow or ask the user to approve the proposed plan.

What is the expected behavior?

_No response_

Additional information

_No response_