Skip to content

codex:review stuck consistently #237

New issue
New issue
Open
Open
codex:review stuck consistently#237

Description

@yinzhou-jc
yinzhou-jc
opened on Apr 17, 2026

I used /codex:review in Claude Code, but it took a long time to return the results. However, when I used codex cli to execute /review (for same diff), it returned quickly.

  1. What could be the reason for this?
  2. Is it possible for me to see the specific status of /codex:review? I suspect that /codex:review got stuck for some reason.
  3. This summary is strange; I didn't ask it to review the working tree. "Summary: Review working tree diff"

----------- /codex:status
Job: review-mo2bmhz5-hpw7ti
Kind: review
Status: running
Phase: investigating
Elapsed: 42m 18s
Summary: Review working tree diff
Actions: /codex:status review-mo2bmhz5-hpw7ti/codex:cancel review-mo2bmhz5-hpw7ti

Image

Activity

  1. rmarquet21 commented on Apr 17, 2026

    @rmarquet21
    rmarquet21
    on Apr 17, 2026

    Same problem !

  2. VladoPortos commented on Apr 17, 2026

    @VladoPortos
    VladoPortos
    on Apr 17, 2026

    Yea it always stuck on this:

    ● Skill(codex:rescue)
  ⎿  Running…e "/home/vladoportos/.claude/plugins/cache/openai-codex/codex/1.0.3/scripts/codex-companion.mjs" task-resume-candidate --json)

     Initializing…escue)           
                                      
✻ Fluttering… (13m 38s · ↓ 1.2k tokens)

    Never exists on its own, no codex token are consumed... when I switch to codex directly it works just fine...

  3. mhkafadar commented on Apr 18, 2026

    @mhkafadar
    mhkafadar
    on Apr 18, 2026

    Same issue.

  4. amit777 commented on Apr 18, 2026

    @amit777
    amit777
    on Apr 18, 2026

    same issue.. it's been happening for about a week or so.

  5. leofang commented on Apr 24, 2026

    @leofang
    leofang
    on Apr 24, 2026

    I asked Claude why it is stuck, this is what Claude replied:

    Codex diagnosis — the plugin has a structural timing problem:

    1. The codex-companion.mjs script launches a Codex task thread and streams progress to an output file
    2. The subagent (Claude Sonnet) that wraps it runs the task via Bash, which returns immediately with "running in background"
    3. The subagent then tries to poll the output file (tail -f, sleep 30 && cat, etc.), but the Claude Code runtime blocks long sleeps and tail -f also runs in background
    4. The subagent hits its turn limit and returns before Codex finishes

    The output file only captures log lines like [codex] Searching: and truncated Assistant message captured: snippets — not the final answer.

    In both runs (adversarial-review and review), Codex did start working (confirmed PR #917 was merged, started searching GitHub), but the subagent couldn't block-wait long enough to collect the result. The codex:codex-rescue skill instructions say "Return the stdout of the task command exactly as-is" but the task runs async and stdout is never fully captured.

    This looks like a mismatch between the codex companion's async execution model and Claude Code's Bash tool (which backgrounds long-running commands).

  6. tgkim-openerd
    added a commit that references this issue on May 18, 2026

    Merge pull request #5 from tgkim-openerd/feat/v2.1.0-status-tail-watch

    8677b96
  7. tgkim-openerd
    added a commit that references this issue on May 27, 2026

    feat(status): /codex:status --tail + --watch with telemetry stitch (P…

    3a270fa
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions