Weird /review output after 0.57.0 update

What version of Codex is running?

codex-cli 0.57.0

What subscription do you have?

Pro

Which model were you using?

GPT-5

What platform is your computer?

Linux 6.6.87.2-microsoft-standard-WSL2 x86_64 x86_64

What issue are you seeing?

The /review output looks like a JSON format or just a weird output after a code review. Example:

{
"findings": [
{
"title": "[P1] Instrument widget countdown with expected test ids",
"body": "The new widget card renders its countdown badge and timer without the data-testid="countdown-badge"/data-
testid="countdown-timer" attributes that every other pending card exposes. All of the shared Playwright helpers
(getCountdownTimer, getCountdownBadge) – which the new pending.widget.spec.ts suite relies on – locate those elements
exclusively via those test ids, so the new widget flow can never satisfy the visibility assertions and the entire spec fails
immediately even though the DOM visually contains the countdown. Please add the same data-testid hooks used in the inline/
redirect cards to the badge and timer container here so the tests and monitoring tooling can see them.",
"confidence_score": 0.61,
"priority": 1,
"code_location": {

PendingWidgetCardV4New.tsx",
"line_range": {
"start": 100,
"end": 167
}
}
},
{
"title": "[P1] Expose widget “Try another method” CTA via data-testid",
"body": "Every pending card (inline, redirect, crypto) tags its secondary CTA with data-testid=\"try-another-method-
"line_range": {
"start": 224,
"overall_correctness": "patch is incorrect",
"overall_explanation": "The new widget payment card omitted the data-testid hooks that all Playwright helpers rely on, so the
freshly added widget E2E suite cannot locate either the countdown elements or the “Try another method” button, causing the
tests to fail even though the UI renders correctly.",
"overall_confidence_score": 0.63
}

What steps can reproduce the bug?

Uploaded thread: 019a6d81-0bed-7dc2-b5f0-a273d0a11b62

What is the expected behavior?

_No response_

Additional information

_No response_