How to Get Support for the Codex Plugin: Official Channels and Troubleshooting

You can get support for the Codex plugin through GitHub Issues in the openai/codex-plugin-cc repository, the OpenAI Developer Forum, Discord #codex-support, or the README documentation, but first verify that Codex is installed, authenticated, and running on Node.js ≥18.18.

The Codex plugin is a tightly-integrated Claude Code extension that delegates code-review and remediation tasks to the local Codex CLI. If you encounter errors while using commands like /codex:review or /codex:rescue in the openai/codex-plugin-cc repository, understanding how to get support efficiently will help you resolve issues quickly. This guide covers the official support channels, diagnostic workflows, and common pitfalls derived directly from the source code.

Understanding the Codex Plugin Architecture

Before filing a support request, it helps to understand how the plugin processes commands. The architecture consists of three main layers that handle your requests:

Slash-Command Dispatcher

The entry points for all user interactions live in the plugins/codex/commands/ directory. Files such as review.md and rescue.md define commands like /codex:review and /codex:rescue. Each command parses flags, builds a job description, and hands execution to the runtime engine.

Runtime Library

Core logic resides under plugins/codex/scripts/lib/. Key modules include:

• state.mjs – Tracks active jobs and persists results.
• process.mjs – Spawns the Codex CLI, streams output, and handles cancellation.
• render.mjs – Formats Codex responses for display in Claude Code.
• git.mjs – Resolves file diffs and prepares the review payload.

Codex CLI Bridge

The plugin invokes the globally-installed codex binary (installed via npm i -g @openai/codex). It forwards prepared payloads to the Codex app-server on your machine, leveraging your existing authentication and configuration as documented in the README.

Official Support Channels for the Codex Plugin

When you need help, use these official channels in order of preference:

GitHub Issues

Open a new issue at https://github.com/openai/codex-plugin-cc/issues. Include the plugin version (npm list @openai/codex), the exact command you ran, and any error output. This is the preferred channel for bug reports and feature requests.

OpenAI Developer Forum

Post questions in the "Codex" category, linking to relevant GitHub issues when applicable. This channel is ideal for architectural questions and integration discussions.

Discord #codex-support

Join via the OpenAI community invite to share logs or screenshots in real-time. Both community members and OpenAI staff monitor this channel for urgent troubleshooting.

Documentation

The README.md contains troubleshooting tips and usage examples updated with each release. Check this first for known issues and configuration guides.

Pre-Flight Checks Before Opening a Support Request

Before reaching out, verify these common pitfalls documented in the repository:

Missing Codex Installation

Run /codex:setup to let the plugin auto-install Codex, or install manually with npm i -g @openai/codex. Without the binary, commands will fail immediately.

Unauthenticated CLI

Execute !codex login to authenticate with a ChatGPT account or API key. Authentication errors typically surface in plugins/codex/scripts/lib/process.mjs when spawning the CLI.

Node Version Mismatch

The plugin requires Node.js ≥18.18 as specified in package.json engines. Older versions cause silent failures during command execution.

How to Gather Diagnostic Information

When reporting issues, provide reproducible evidence using these commands:

# Verify the plugin can locate the Codex binary

/codex:setup

# Expected output: "Codex is ready" or installation prompt

# Run a review in background mode to generate a traceable job ID

/codex:review --background
/codex:status

# Capture the job ID (e.g., task-a1b2c3) from the status output

# Export raw results for debugging

/codex:result task-a1b2c3 > codex-output.txt

If you encounter Error: Codex binary not found or Permission denied, the error originates from plugins/codex/scripts/lib/codex.mjs, which resolves the binary path. Copy the full console output—including the stack trace—into your GitHub issue.

Summary

• The openai/codex-plugin-cc repository provides four support channels: GitHub Issues, OpenAI Developer Forum, Discord #codex-support, and the README documentation.
• Always include your plugin version, Node.js version, and exact command syntax when requesting help.
• Run /codex:setup to verify installation, !codex login to check authentication, and ensure Node.js ≥18.18 before filing issues.
• Diagnostic data from /codex:status and /codex:result helps maintainers reproduce bugs in process.mjs and codex.mjs.

Frequently Asked Questions

Where should I report bugs in the Codex plugin?

Report bugs in the GitHub Issues section of the openai/codex-plugin-cc repository. Include your plugin version, the command that failed, and any error output from Claude Code to help maintainers trace issues in the runtime library.

Why does the plugin say "Codex binary not found"?

This error originates in plugins/codex/scripts/lib/codex.mjs when the plugin cannot locate the globally installed codex CLI. Run /codex:setup to auto-install or manually install with npm i -g @openai/codex, then verify the path resolves correctly.

How do I check if my Node.js version is compatible with the Codex plugin?

The plugin requires Node.js ≥18.18 as defined in package.json. Run node --version in your terminal. If your version is older, upgrade Node.js before using the plugin to avoid runtime failures in process.mjs.

Can I get help with Codex CLI authentication issues through the plugin support channels?

Yes. Authentication errors are supported topics. Ensure you run !codex login to authenticate with your ChatGPT account or API key, and mention any authentication errors when posting in GitHub Issues or Discord.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}