Skip to content

Review fails due to unknown sandboxing variant #3

Closed

Description

@arvidkahl

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

Image Image

Activity

  1. SatyKrish commented on Mar 30, 2026

    @SatyKrish

    I get similar issue with sandbox environment.

    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.
    
  2. dkundel-openai commented on Mar 30, 2026

    @dkundel-openai
    Collaborator

    Thanks for flagging. I'm looking into this!

  3. dkundel-openai commented on Mar 30, 2026

    @dkundel-openai
    Collaborator

    @arvidkahl inside bash can you run which codex and codex --version? There might be a version mismatch happening here.

  4. arvidkahl commented on Mar 30, 2026

    @arvidkahl
    Author

    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.

  5. dkundel-openai commented on Mar 30, 2026

    @dkundel-openai
    Collaborator

    Thank you! That's definitely odd since we moved from readOnly to read-only back in December. Will do some more digging with Codex

  6. nialloriordanroo commented on Mar 30, 2026

    @nialloriordanroo

    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.

    Summary of steps that got the review working:

    1. Run codex login
    2. Upgrade codex CLI: npm install -g @openai/codex --force
    3. Kill any stale shared broker session
    4. Run /codex:review
  7. dkundel-openai commented on Mar 31, 2026

    @dkundel-openai
    Collaborator

    @arvidkahl van you let me know if the instructions above fixed it?

    @SatyKrish you might be running into the same issue as #18

  8. arvidkahl commented on Mar 31, 2026

    @arvidkahl
    Author

    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.

  9. added a commit that references this issue on May 9, 2026
    7808c92
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