/review doesn't complete. It returns with "continue?" instead of a review.

[turtle261]

What version of Codex CLI is running?

codex-cli 0.132.0

What subscription do you have?

Plus

Which model were you using?

GPT-5.3-codex (xhigh)

What platform is your computer?

Linux 6.18.31-gentoo-dist x86_64 Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz

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

Alacritty

Codex doctor report

What issue are you seeing?

Asking for a PR-style review with /review doesn't return any review, instead, it says "continue?" for no reason -- there is no rate limit issue or anything, it just returned "continue?" as the response text for the review. This is wasting usage.

What steps can reproduce the bug?

Was done in a fresh session, by /clear, then /review, click PR-style, and selected the merge-base to review against. It did a few git diffs, then said "continue"

What is the expected behavior?

A review output/comment, or even "Looks good to me, no issues found"..

Additional information

No response

[yui-stingray]

I took a quick look at origin/main as of 7d47056. I have not reproduced this locally, so this is only a plausible code-path explanation, not a confirmed root cause.

In codex-rs/core/src/tasks/review.rs:

• start_review_conversation starts the delegated review turn with final_output_json_schema set to None.
• process_review_events reads TurnComplete.last_agent_message and passes it to parse_review_output_event.
• parse_review_output_event first tries to parse a ReviewOutputEvent JSON object, but if parsing fails it falls back to ReviewOutputEvent { overall_explanation: text.to_string(), ..Default::default() }.
• exit_review_mode then records/renders that ReviewOutputEvent as the review output.

That means if the reviewer’s final assistant message is plain text such as continue?, the current fallback path appears able to surface it as the review output rather than treating it as malformed structured reviewer output.

There is already coverage for the plain-text fallback behavior (review_op_with_plain_text_emits_review_fallback). If this behavior is not desired for low-information reviewer replies, the test expectation likely needs to change, or a narrower test could cover messages like continue? and assert the intended behavior, whether that should be retrying, failing clearly, or showing an explicit “review output was malformed” message.