Codex++ v1.2.3

Codex++ can be thought of as an ‘external enhancement launcher’ for the Codex App. It solves the issue where the plugin entry becomes grayed out after logging into Codex with an API Key, enabling plugin access. It also allows for session management and deletion. Most importantly, it can redirect model requests to your specified API proxy, meaning Codex can directly use the DeepSeek large model.

Its principle is not to modify Codex’s installation files, but to launch Codex with its own launcher and inject enhancement scripts via CDP.

Core Features

Simply put, it focuses on several issues that the official Codex team hasn’t fixed, which users have been complaining about:

Unlock Plugin Entry

In the native Codex, after logging in with an API Key, the plugin entry is grayed out, prompting ‘Login to ChatGPT required.’ Codex++ bypasses this check logic, allowing normal plugin installation and Skills usage in API Key mode.

Permanent Session Deletion

The original session list only has ‘Archive,’ with no true delete button. Finding things becomes very difficult as sessions pile up. After Codex++ injection, a delete button appears directly when hovering over a session in the list; one click and it’s gone.

Proxy Injection (The Main Event)

This is its most powerful feature:redirecting Codex’s model requests to your specified API proxy.This means your Codex can directly use other large models like DeepSeek, Claude, Gemini, etc., freeing you from token worries. The configuration is written into ~/.codex/config.toml, and you can switch back to the official login state anytime.

Markdown Export / Timeline / Project Move

Sessions can be exported to Markdown for archiving, you can view the conversation Timeline for review, and migrate projects across directories—all small features that make you wonder ‘why didn’t the official version include these?’

User Scripts

Supports injecting custom JS, similar to Tampermonkey-style usage. Experts who can write scripts can extend functionality themselves.

Provider Sync

After switching model providers, the metadata of old sessions remains, so you won’t lose visibility just because you changed keys.

Usage Tutorial:

I’ll use my M3 MacBook as an example. The process is basically the same for Windows users, just with different packages.

Step 1: Install Codex Itself

If you haven’t installed it yet, download it first from the official OpenAI website. Codex++ does not provide Codex itself.

Step 2: Download Codex++

Go to the GitHub Releases page and download the corresponding package for your system:

• macOS Apple Silicon → CodexPlusPlus-*-macos-arm64.dmg
• macOS Intel → CodexPlusPlus-*-macos-x64.dmg
• Windows → CodexPlusPlus-*-windows-x64-setup.exe

Currently the latest is v1.2.3(released June 5, 2026).

Step 3: Installation

For DMG, just drag it to Applications. For Windows exe, follow the installation steps;it will create desktop and Start Menu shortcuts.

Step 4: Configure Proxy (Optional but Recommended)

Open ‘Codex++ Management Tool’ → Provider Configuration → Add Provider, fill in your Base URL and Key.

Here are two common examples:

• DeepSeek: Fill in Base URL as https://api.deepseek.com/v1, upstream protocol select Chat Completions(do not select Responses)
• Agnes: Fill in Base URL as https://apihub.agnes-ai.com/v1, model select agnes-2.0-flash

After saving, click ‘Use,’ then click the restart button in the top-right corner. Wait for Codex++ to relaunch Codex, and it will take effect.

Step 5: Daily Use

From now on,launch from the Codex++ icon(not the original Codex). A status indicator for Codex++ will appear in the top menu bar, showing backend connection status, allowing configuration switching, and viewing logs.

💸 Pitfall Warning (Important):

• Unsigned macOS Packagemay trigger ‘damaged and cannot be opened.’ Execute these two commands in Terminal to unlock: bashbashsudo xattr -rd com.apple.quarantine "/Applications/Codex++.app" sudo xattr -rd com.apple.quarantine "/Applications/Codex++ 管理工具.app"The latest version v1.2.3 has already fixed this issue.
• Windows Port Occupiedcan cause startup failure. The latest version has also fixed the issue of abnormal single-instance port occupation.
• Occasionally the launcher may freeze. Just kill the Codex and Codex++ processes in Task Manager and restart—this is a minor issue reported by many in the community.