openai / openai/codex-plugin-cc

the codex tool seems not writing review output reliably

Open
#207 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
33.3k
Forks
2.3k
PR merge metrics
No merged PRs in 30d

Description

❯ /codex:adversarial-review --background --base main look for race conditions and question the chosen approach

⏺ Bash(node "/Users/simon/.claude/plugins/cache/openai-codex/codex/1.0.3/scripts/codex-companion.mjs" adversarial-review "--background --base main look for race condit…)
⎿  Running in the background (↓ to manage)

⏺ Codex adversarial review started in the background. Check /codex:status for progress.

❯ /codex:status

⏺ ┌────────────────────────┬────────────────────┬─────────┬─────────┬─────────┬──────────────────────────────────────┬──────────────────────────────────────────────────────────────────┐
│ Job │ Kind │ Status │ Phase │ Elapsed │ Summary │ Actions │
├────────────────────────┼────────────────────┼─────────┼─────────┼─────────┼──────────────────────────────────────┼──────────────────────────────────────────────────────────────────┤
│ review-mnus37r6-c6cllg │ adversarial-review │ running │ running │ 13s │ Adversarial Review branch diff │ /codex:status review-mnus37r6-c6cllg · /codex:cancel │
│ │ │ │ │ │ against main │ review-mnus37r6-c6cllg │
└────────────────────────┴────────────────────┴─────────┴─────────┴─────────┴──────────────────────────────────────┴──────────────────────────────────────────────────────────────────┘

⏺ Background command "Codex adversarial review" completed (exit code 0)

⏺ The Codex adversarial review has completed. Let me fetch the results.

Read 1 file (ctrl+o to expand)

⏺ The raw output is all [codex] trace lines without the final review text. Let me check the job log for the actual review output.

Read 2 files, listed 3 directories (ctrl+o to expand)

⏺ Bash(node "/Users/simon/.claude/plugins/cache/openai-codex/codex/1.0.3/scripts/codex-companion.mjs" status review-mnus37r6-c6cllg 2>&1)
⎿  # Codex Job Status

 - review-mnus37r6-c6cllg | running | adversarial-review | Codex Adversarial Review
 … +12 lines (ctrl+o to expand)

⏺ Bash(ps aux | grep 16329 | grep -v grep)
⎿  No matches found

⏺ Bash(node "/Users/simon/.claude/plugins/cache/openai-codex/codex/1.0.3/scripts/codex-companion.mjs" status review-mnus37r6-c6cllg 2>&1)
⎿  # Codex Job Status

 - review-mnus37r6-c6cllg | running | adversarial-review | Codex Adversarial Review
 … +12 lines (ctrl+o to expand)

⏺ The Codex process exited (pid 16329 is gone) but the job JSON wasn't updated to "completed" - it looks like the review output may not have been captured. Let me try to retrieve the final
response from the Codex session directly.

⏺ Bash(codex resume 019d7e33-11d0-7332-8a96-d249109ea270 --dump 2>&1 | head -500)
⎿  error: unexpected argument '--dump' found

   tip: to pass '--dump' as a value, use '-- --dump'
 … +4 lines (ctrl+o to expand)

⏺ Bash(codex --help 2>&1 | head -30)
⎿  Codex CLI

 If no subcommand is specified, options will be forwarded to the interactive CLI.
 … +26 lines (ctrl+o to expand)

⏺ Bash(codex debug --help 2>&1)
⎿  Debugging tools

 Usage: codex debug [OPTIONS] <COMMAND>
 … +23 lines (ctrl+o to expand)

Searched for 6 patterns, listed 1 directory (ctrl+o to expand)

⏺ The Codex process exited but it appears the review text wasn't persisted to a retrievable file - the companion script's background task captured only the trace/progress lines, not the
final model output. The Codex session ID is 019d7e33-11d0-7332-8a96-d249109ea270 if you want to try resuming it interactively with codex resume 019d7e33-11d0-7332-8a96-d249109ea270.

Let me run the review again in the foreground so we actually capture the output this time.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with scripts/codex-companion.mjs and trace the background adversarial-review command through its job-status and output handling. Reproduce the shown run, checking the captured trace, job JSON, and Codex session output. Done means the review reaches a completed state and its final review text is reliably persisted and retrievable.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.