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
{{ message }}
Repository navigation
Plugin install fails on Windows with corrupted error message #113
Summary:
When running /plugin install codex@openai-codex on Windows with Node.js v20.10.5, the installation fails and outputs corrupted or unreadable error data instead of a normal error message.
Environment:
OS: Windows
Node.js version: v20.10.5
Steps to reproduce:
Open terminal on Windows.
Run /plugin install codex@openai-codex.
Observe the installation fails with a binary or corrupted error message (example output provided below).
Expected behavior:
The plugin should install successfully or display a clear, readable error message if it fails.
Actual behavior:
The command fails and outputs binary/corrupted data instead of a human-readable error message.
Example error output:
H�l]�#�U,�;... (binary/unreadable data)
Additional notes:
User was unable to provide more readable output.
This issue blocks installation and prevents further setup/use.
Runs a normal Codex review on your current work. It gives you the same quality of code review as running /review inside Codex directly.
Note
Code review especially for multi-file changes might take a while. It's generally recommended to run it in the background.
Use it when you want:
a review of your current uncommitted changes
a review of your branch compared to a base branch like main
Use --base <ref> for branch review. It also supports --wait and --background. It is not steerable and does not take custom focus text. Use /codex:adversarial-review when you want to challenge a specific decision or risk area.
Examples:
/codex:review
/codex:review --base main
/codex:review --background
This command is read-only and will not perform any changes. When run in the background you can use /codex:status to check on the progress and /codex:cancel to cancel the ongoing task.
/codex:adversarial-review
Runs a steerable review that questions the chosen implementation and design.
It can be used to pressure-test assumptions, tradeoffs, failure modes, and whether a different approach would have been safer or simpler.
It uses the same review target selection as /codex:review, including --base <ref> for branch review.
It also supports --wait and --background. Unlike /codex:review, it can take extra focus text after the flags.
Use it when you want:
a review before shipping that challenges the direction, not just the code details
review focused on design choices, tradeoffs, hidden assumptions, and alternative approaches
pressure-testing around specific risk areas like auth, data loss, rollback, race conditions, or reliability
Examples:
/codex:adversarial-review
/codex:adversarial-review --base main challenge whether this was the right caching and retry design
/codex:adversarial-review --background look for race conditions and question the chosen approach
This command is read-only. It does not fix code.
/codex:rescue
Hands a task to Codex through the codex:codex-rescue subagent.
Use it when you want Codex to:
investigate a bug
try a fix
continue a previous Codex task
take a faster or cheaper pass with a smaller model
Note
Depending on the task and the model you choose these tasks might take a long time and it's generally recommended to force the task to be in the background or move the agent to the background.
It supports --background, --wait, --resume, and --fresh. If you omit --resume and --fresh, the plugin can offer to continue the latest rescue thread for this repo.
Examples:
/codex:rescue investigate why the tests started failing
/codex:rescue fix the failing test with the smallest safe patch
/codex:rescue --resume apply the top fix from the last run
/codex:rescue --model gpt-5.4-mini --effort medium investigate the flaky integration test
/codex:rescue --model spark fix the issue quickly
/codex:rescue --background investigate the regression
You can also just ask for a task to be delegated to Codex:
Ask Codex to redesign the database connection to be more resilient.
Notes:
if you do not pass --model or --effort, Codex chooses its own defaults.
if you say spark, the plugin maps that to gpt-5.3-codex-spark
follow-up rescue requests can continue the latest Codex task in the repo
/codex:status
Shows running and recent Codex jobs for the current repository.
Examples:
/codex:status
/codex:status task-abc123
Use it to:
check progress on background work
see the latest completed job
confirm whether a task is still running
/codex:result
Shows the final stored Codex output for a finished job.
When available, it also includes the Codex session ID so you can reopen that run directly in Codex with codex resume <session-id>.
Examples:
/codex:result
/codex:result task-abc123
/codex:cancel
Cancels an active background Codex job.
Examples:
/codex:cancel
/codex:cancel task-abc123
/codex:setup
Checks whether Codex is installed and authenticated.
If Codex is missing and npm is available, it can offer to install Codex for you.
You can also use /codex:setup to manage the optional review gate.
When the review gate is enabled, the plugin uses a Stop hook to run a targeted Codex review based on Claude's response. If that review finds issues, the stop is blocked so Claude can address them first.
Warning
The review gate can create a long-running Claude/Codex loop and may drain usage limits quickly. Only enable it when you plan to actively monitor the session.
Typical Flows
Review Before Shipping
/codex:review
Hand A Problem To Codex
/codex:rescue investigate why the build is failing in CI
Start Something Long-Running
/codex:adversarial-review --background
/codex:rescue --background investigate the flaky test
If you want to change the default reasoning effort or the default model that gets used by the plugin, you can define that inside your user-level or project-level config.toml. For example to always use gpt-5.4-mini on high for a specific project you can add the following to a .codex/config.toml file at the root of the directory you started Claude in:
model = "gpt-5.4-mini"model_reasoning_effort = "xhigh"
Delegated tasks and any stop gate run can also be directly resumed inside Codex by running codex resume either with the specific session ID you received from running /codex:result or /codex:status or by selecting it from the list.
This way you can review the Codex work or continue the work there.
FAQ
Do I need a separate Codex account for this plugin?
If you are already signed into Codex on this machine, that account should work immediately here too. This plugin uses your local Codex CLI authentication.
If you only use Claude Code today and have not used Codex yet, you will also need to sign in to Codex with either a ChatGPT account or an API key. Codex is available with your ChatGPT subscription, and codex login supports both ChatGPT and API key sign-in. Run /codex:setup to check whether Codex is ready, and use !codex login if it is not.
I could not reproduce this; it is an install-time error. Could you retry on the fork v1.4.1 (https://github.com/CBEPX/codex-plugin-cc/releases/tag/v1.4.1) with /plugin marketplace add CBEPX/codex-plugin-cc and /plugin install codex@cbepx? If it still fails, please report the exact error text (screenshot or raw bytes if garbled), your OS and console code page, codex --version, and the /codex:status --json output if the plugin loads.
Activity
terad-alrowes commentedon Apr 2, 2026
H�l]�#�U,�;... (binary/unreadable data)
terad-alrowes commentedon Apr 2, 2026
Arabic_Book_Master_Template.docx
terad-alrowes commentedon Apr 2, 2026
Codex plugin for Claude Code
Use Codex from inside Claude Code for code reviews or to delegate tasks to Codex.
This plugin is for Claude Code users who want an easy way to start using Codex from the workflow
they already have.
What You Get
/codex:reviewfor a normal read-only Codex review/codex:adversarial-reviewfor a steerable challenge review/codex:rescue,/codex:status,/codex:result, and/codex:cancelto delegate work and manage background jobsRequirements
Install
Add the marketplace in Claude Code:
Install the plugin:
Reload plugins:
Then run:
/codex:setupwill tell you whether Codex is ready. If Codex is missing and npm is available, it can offer to install Codex for you.If you prefer to install Codex yourself, use:
If Codex is installed but not logged in yet, run:
!codex loginAfter install, you should see:
codex:codex-rescuesubagent in/agentsOne simple first run is:
Usage
/codex:reviewRuns a normal Codex review on your current work. It gives you the same quality of code review as running
/reviewinside Codex directly.Note
Code review especially for multi-file changes might take a while. It's generally recommended to run it in the background.
Use it when you want:
mainUse
--base <ref>for branch review. It also supports--waitand--background. It is not steerable and does not take custom focus text. Use/codex:adversarial-reviewwhen you want to challenge a specific decision or risk area.Examples:
This command is read-only and will not perform any changes. When run in the background you can use
/codex:statusto check on the progress and/codex:cancelto cancel the ongoing task./codex:adversarial-reviewRuns a steerable review that questions the chosen implementation and design.
It can be used to pressure-test assumptions, tradeoffs, failure modes, and whether a different approach would have been safer or simpler.
It uses the same review target selection as
/codex:review, including--base <ref>for branch review.It also supports
--waitand--background. Unlike/codex:review, it can take extra focus text after the flags.Use it when you want:
Examples:
/codex:adversarial-review /codex:adversarial-review --base main challenge whether this was the right caching and retry design /codex:adversarial-review --background look for race conditions and question the chosen approachThis command is read-only. It does not fix code.
/codex:rescueHands a task to Codex through the
codex:codex-rescuesubagent.Use it when you want Codex to:
Note
Depending on the task and the model you choose these tasks might take a long time and it's generally recommended to force the task to be in the background or move the agent to the background.
It supports
--background,--wait,--resume, and--fresh. If you omit--resumeand--fresh, the plugin can offer to continue the latest rescue thread for this repo.Examples:
You can also just ask for a task to be delegated to Codex:
Notes:
--modelor--effort, Codex chooses its own defaults.spark, the plugin maps that togpt-5.3-codex-spark/codex:statusShows running and recent Codex jobs for the current repository.
Examples:
Use it to:
/codex:resultShows the final stored Codex output for a finished job.
When available, it also includes the Codex session ID so you can reopen that run directly in Codex with
codex resume <session-id>.Examples:
/codex:cancelCancels an active background Codex job.
Examples:
/codex:setupChecks whether Codex is installed and authenticated.
If Codex is missing and npm is available, it can offer to install Codex for you.
You can also use
/codex:setupto manage the optional review gate.Enabling review gate
When the review gate is enabled, the plugin uses a
Stophook to run a targeted Codex review based on Claude's response. If that review finds issues, the stop is blocked so Claude can address them first.Warning
The review gate can create a long-running Claude/Codex loop and may drain usage limits quickly. Only enable it when you plan to actively monitor the session.
Typical Flows
Review Before Shipping
Hand A Problem To Codex
/codex:rescue investigate why the build is failing in CIStart Something Long-Running
/codex:adversarial-review --background /codex:rescue --background investigate the flaky testThen check in with:
Codex Integration
The Codex plugin wraps the Codex app server. It uses the global
codexbinary installed in your environment and applies the same configuration.Common Configurations
If you want to change the default reasoning effort or the default model that gets used by the plugin, you can define that inside your user-level or project-level
config.toml. For example to always usegpt-5.4-minionhighfor a specific project you can add the following to a.codex/config.tomlfile at the root of the directory you started Claude in:Your configuration will be picked up based on:
~/.codex/config.toml.codex/config.tomlCheck out the Codex docs for more configuration options.
Moving The Work Over To Codex
Delegated tasks and any stop gate run can also be directly resumed inside Codex by running
codex resumeeither with the specific session ID you received from running/codex:resultor/codex:statusor by selecting it from the list.This way you can review the Codex work or continue the work there.
FAQ
Do I need a separate Codex account for this plugin?
If you are already signed into Codex on this machine, that account should work immediately here too. This plugin uses your local Codex CLI authentication.
If you only use Claude Code today and have not used Codex yet, you will also need to sign in to Codex with either a ChatGPT account or an API key. Codex is available with your ChatGPT subscription, and
codex loginsupports both ChatGPT and API key sign-in. Run/codex:setupto check whether Codex is ready, and use!codex loginif it is not.Does the plugin use a separate Codex runtime?
No. This plugin delegates through your local Codex CLI and Codex app server on the same machine.
That means:
Will it use the same Codex config I already have?
Yes. If you already use Codex, the plugin picks up the same configuration.
Can I keep using my current API key or base URL setup?
Yes. Because the plugin uses your local Codex CLI, your existing sign-in method and config still apply.
If you need to point the built-in OpenAI provider at a different endpoint, set
openai_base_urlin your Codex config.docs(ultraplan): handoff §4.4 current limitations + §5 B2 re-verifica…
fix(plugin): close upstream OPEN backlog — openai#59 state migration, o…
Merge pull request #7: close upstream OPEN backlog (openai#59 / opena…
docs(changelog): sync Unreleased with PR #3-#8
CBEPX commentedon Sep 29, 2026
I could not reproduce this; it is an install-time error. Could you retry on the fork v1.4.1 (https://github.com/CBEPX/codex-plugin-cc/releases/tag/v1.4.1) with
/plugin marketplace add CBEPX/codex-plugin-ccand/plugin install codex@cbepx? If it still fails, please report the exact error text (screenshot or raw bytes if garbled), your OS and console code page,codex --version, and the/codex:status --jsonoutput if the plugin loads.