You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After a fresh installation and being logged into Codex inside of Claude Code, when asking for a /codex:review, the companion script seems to transmit the wrong variant for the sandbox value that should be spawned. Hence the review command errors. codex-cli 0.117.0
The Codex reviewer couldn't access the shell in its sandbox. The review output is above — it was unable to execute due to sandbox restrictions in this environment.
The binary from which codex also returns codex-cli 0.117.0 (if it helps, it's located at /Users/arvidkahl/Library/Application Support/Herd/config/nvm/versions/node/v21.7.3/bin/codex as I run this through Herd and inside PHPStorm.
I had the same issue and was able to resolve it. Summary below:
Root cause: Old process still running after upgrading
Codex version too old:
codex-cli 0.57.0 (installed via Homebrew) rejected the sandbox variant sent by the plugin:
Invalid request: unknown variant read-only, expected one of readOnly, workspaceWrite, dangerFullAccess
Fix: Upgrade to the latest CLI: npm install -g @openai/codex --strict-ssl=false --force
This updated from 0.57.0 → 0.117.0.
Old process still running:
After upgrading, the old broker process (started with CLI 0.57.0) was still running and handling requests. The review kept failing until the stale session was killed: kill $(jq -r .pid ~/.claude/plugins/... /broker.json)
The next /codex:review started a fresh session with the upgraded CLI and succeeded.
It is resolved now, @dkundel-openai. The instructions fixed it (as they sent me and my Claude hunting for PIDs to kill).
After killing many processes several times, I had the Codex app running, which I needed to close. Even then, the app server in the background still remained alive after being killed through the ! kill xxxxx yyyyy zzzzz in-session command. I had Claude figure out which process IDs to kill and then do it with a kill -9 command that left no Codex processes left, and then the review command started working.
Activity
SatyKrish commentedon Mar 30, 2026
I get similar issue with sandbox environment.
dkundel-openai commentedon Mar 30, 2026
Thanks for flagging. I'm looking into this!
dkundel-openai commentedon Mar 30, 2026
@arvidkahl inside bash can you run
which codexandcodex --version? There might be a version mismatch happening here.arvidkahl commentedon Mar 30, 2026
The binary from
which codexalso returnscodex-cli 0.117.0(if it helps, it's located at/Users/arvidkahl/Library/Application Support/Herd/config/nvm/versions/node/v21.7.3/bin/codexas I run this through Herd and inside PHPStorm.dkundel-openai commentedon Mar 30, 2026
Thank you! That's definitely odd since we moved from
readOnlytoread-onlyback in December. Will do some more digging with Codexnialloriordanroo commentedon Mar 30, 2026
I had the same issue and was able to resolve it. Summary below:
Root cause: Old process still running after upgrading
Codex version too old:
codex-cli 0.57.0 (installed via Homebrew) rejected the sandbox variant sent by the plugin:
Invalid request: unknown variant
read-only, expected one ofreadOnly,workspaceWrite,dangerFullAccessFix: Upgrade to the latest CLI:
npm install -g @openai/codex --strict-ssl=false --forceThis updated from 0.57.0 → 0.117.0.
Old process still running:
After upgrading, the old broker process (started with CLI 0.57.0) was still running and handling requests. The review kept failing until the stale session was killed:
kill $(jq -r .pid ~/.claude/plugins/... /broker.json)The next /codex:review started a fresh session with the upgraded CLI and succeeded.
Summary of steps that got the review working:
npm install -g @openai/codex --force/codex:reviewdkundel-openai commentedon Mar 31, 2026
@arvidkahl van you let me know if the instructions above fixed it?
@SatyKrish you might be running into the same issue as #18
arvidkahl commentedon Mar 31, 2026
It is resolved now, @dkundel-openai. The instructions fixed it (as they sent me and my Claude hunting for PIDs to kill).
After killing many processes several times, I had the Codex app running, which I needed to close. Even then, the app server in the background still remained alive after being killed through the
! kill xxxxx yyyyy zzzzzin-session command. I had Claude figure out which process IDs to kill and then do it with akill -9command that left no Codex processes left, and then the review command started working.fix(stability): W1 adversarial-review follow-ups — 3 edge cases hardened
feat(status): /codex:status --tail + --watch with telemetry stitch (P…
feat(spawn): mitigate Codex JSONL parser crash on non-UTF-8 hosts (PR…
Merge pull request #3 from opnd-io/feat/upstream-port-tier1-8high
fix(plugin): land workstream B delta — repair broken 17385e4 + PR #3 …
Merge pull request #4: land workstream B delta + PR #3 review fixes
fix(plugin): pair-readiness A1-A4 — bound approval wait, default-on w…
docs(changelog): sync Unreleased with PR #3-#8
Merge pull request #9: changelog sync PR #3-#8
feat: reliability backlog — 4 batches + SessionEnd background-job dec…
fix: reliability follow-up — broker shutdown gate, idle-turn interrup…
docs: revise spec & plan per adversarial review (test-validity fixes)