Allow /review to be queued while a task is in progress

What feature would you like to see?

I would like Codex CLI to allow the /review slash command (especially Review uncommitted changes) to be queued while a task is in progress, instead of showing the error:

'/review' is disabled while a task is in progress.

Concretely, when I type /review during a long-running task, I want Codex to accept it and schedule it as the next task once the current one finishes, similar to how prompts are queued.

Motivation

My typical workflow is:

1. Start a long-running task (for example, “implement X feature and run tests”).
2. While Codex is still working, I realize I want a code review of my local changes right after it finishes.
3. I try to run /review uncommitted changes immediately, but Codex rejects it with "/review is disabled while a task is in progress."

This forces me to sit and wait until the current task completes, then manually type /review again. It breaks the flow and makes it harder to batch work: I’d like to set up “do this task, then immediately review my changes” in one go.

Desired behavior

• Allow slash commands like /review to be queued while a task is in progress.
• When a task is running, /review should not fail; instead it should:
• Acknowledge that it has been queued.
• Automatically run as soon as the current task completes.
• Ideally this could follow the same queueing semantics as normal prompts (as requested in “Queue slash commands”).

This would make it easy to create small pipelines like:

• “Refactor this module” → then /review uncommitted changes
• “Implement this endpoint and run tests” → then /review against base branch

Additional context

• Environment: Codex CLI on a local repo.
• Workflow: heavy use of /review uncommitted changes between tasks.
• Related: There is an existing feature request to queue slash commands while a task is in progress; my main use case is specifically about /review, since it is often the very next step after a long-running task finishes.

Additional information

_No response_