Auto-review denial missing from /approve; unable to request scoped re-review

What version of Codex CLI is running?

Codex CLI v0.153.4; connected app-server v0.153.4.

What subscription do you have?

ChatGPT Pro 20x

Which model were you using?

gpt-6-astra with xhigh reasoning; subsequently switched to gpt-5.6-terra with xhigh reasoning. The unresolved approval blocker persisted after switching.

What platform is your computer?

Windows host running Ubuntu under WSL. Exact Windows build, WSL version and Linux kernel version are not available in the retained information.

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

Terminal emulator name/version and multiplexer status are unknown. Codex CLI runs inside WSL and connects to a local Codex app-server. The same session is also accessed remotely through ChatGPT on iPhone.

Codex doctor report

What issue are you seeing?

A previously denied local code-edit action is unavailable in the /approve picker, leaving no identified way to request action-specific re-review.

The archived request concerned one bundled pipeline.py patch for:

• atomic metadata-generation refresh;
• synthetic instrument-specific funding/settlement annotations;
• isolated SHADOW_ONLY trailing integration.

The recorded rejection states:
“Although explicitly requested and locally scoped, this patch adds outcome-replay/cash-flow and candidate-selection mechanics prohibited by the active R2 Phase 0.1 invariants.”

The session originated in the main repository, while the intended implementation is in a sibling worktree with an offline-task addendum. The reviewer’s complete loaded instruction chain is unknown, so I cannot establish whether this is a project-scope interpretation problem, a configuration issue, or another enforced restriction.

A separate Decimal cleanup action WAS selectable in /approve. I approved it, its reviewed retry was accepted, and the patch and focused tests completed successfully.

However, the metadata/funding/shadow-trailing action was absent during two picker inspections. Only an archived description and denial remain; the original complete tool-call payload and approval ID are unavailable.

Please explain the missing action and provide the supported procedure to restore its review or submit a fresh scoped request. I am not requesting disabled safeguards or broader access.

All permitted application work is preserved in local commit:
fc58b76d80d8d2251e310480d87afa0b634c0e51

What steps can reproduce the bug?

Uploaded thread: 01a0792a-a466-7fc2-be5d-b079e14ae476

What is the expected behavior?

No response

Additional information

Feedback upload completed successfully. The upload dialog listed codex-doctor-report.json, session logs and the auto-review rollout among its diagnostics.

Uploaded reporting thread:
01a0792a-a466-7fc2-be5d-b079e14ae476

The full doctor-report JSON is not available to paste from my phone.

Observed sequence in the affected session; a standalone minimal reproduction is not available:

1. Run Codex CLI connected to a local app-server under Windows/WSL. Both reported version v0.153.4. Permissions were set to “Approve for me.”
2. During an owner-authorized offline implementation task in a sibling worktree, an escalated tool request attempted a bundled pipeline.py change for metadata-generation refresh, synthetic funding/settlement annotations and SHADOW_ONLY trailing.
3. Auto-review rejected the request, citing active R2 Phase 0.1 project restrictions.
4. Later, open /approve in the affected session. A separate cleanup action and unrelated older actions are visible, but the bundled metadata/funding/shadow-trailing action is absent.
5. Approve the separate cleanup action. Its reviewed retry succeeds.
6. Inspect /approve again. The bundled action is still absent.
7. Request continuation. Codex stops before implementation because the bundled denial remains unresolved and no selectable approval identity is available.

Expected:
A supported way to request scoped re-review, or a clear explanation of why the action is unavailable and what supported recovery procedure applies.

Actual:
The archived denial is treated as effective, but its action cannot be selected for approval. Why it is absent remains unknown.

Uploaded reporting thread:
01a0792a-a466-7fc2-be5d-b079e14ae476

Recorded original-denial time window:
2026-09-07T19:34:49Z–19:37:32Z

The original denied action’s owning thread and approval ID are unknown. The uploaded reporting thread should not be assumed to identify them.

Feedback upload completed and included session/auto-review diagnostics. No denied action was recreated to reproduce this issue.

Start with the /approve picker and the local app-server approval flow described in the issue. Compare how the selectable Decimal cleanup action is represented with the archived metadata/funding/shadow-trailing denial, using the uploaded reporting thread and session diagnostics if available. Done means documenting why the denied action is absent and providing a supported scoped re-review or recovery procedure.