Codex++: An Open-Source Enhancement Tool That Unlocks Hidden Plugins and Session Management in OpenAI Codex

OpenAI's Codex desktop app is powerful, but it comes with significant limitations in practice — plugins can't be invoked in API mode, sessions can't be deleted, and there's no export functionality. The open-source project Codex++ was created to address exactly these pain points. It dynamically patches the original Codex application to unlock a range of hidden or restricted features.

Why Do You Need Codex++?

OpenAI Codex is an AI programming assistant platform from OpenAI whose desktop app allows developers to interact with AI using natural language for code writing, debugging, and project management. Codex supports two main usage modes: a standard mode using your official OpenAI account login, and an API mode that connects via a custom API Key. API mode is particularly important for enterprise users and developers who need fine-grained control over usage and costs, but the official version imposes significant feature restrictions in this mode — which has become the community's primary source of frustration.

The original Codex desktop app has notable shortcomings in the following areas:

• Lack of session management: Unable to delete existing conversation records, leading to an increasingly cluttered interface over time
• Restricted API mode features: When using custom API mode, the plugin system is completely locked — Computer Use, Chrome, GitHub, and other plugins are all inaccessible
• No export capability: Unable to export conversation content to universal formats like Markdown, hindering knowledge preservation and team collaboration

As a community-driven enhancement tool, Codex++ precisely fills these functional gaps. The project has already attracted numerous contributors on GitHub and is in a state of active development and rapid iteration.

Codex++ Core Features Explained

Enhanced Session Management

The most immediate improvement Codex++ brings is completing the session management features missing from the original:

• Delete sessions: Clean up conversation records you no longer need, keeping your workspace tidy
• Export sessions: Export conversation content as Markdown files for archiving, sharing, or further editing
• Move sessions: Migrate sessions from one project to another for more flexible project organization

These seemingly basic features are completely absent in the original Codex. Codex++'s additions provide a qualitative improvement to the daily user experience.

Unlocking Plugins in API Mode

This is Codex++'s most critical capability. The original Codex blocks the entire plugin system (also known as Tool Use) in API mode, but Codex++ bypasses this restriction through dynamic patching, allowing users to freely invoke Computer Use, Chrome, GitHub, and other plugins even in API mode.

It's worth explaining the technical significance of these plugins. Codex's plugin system is the key mechanism that enables AI to not only generate text but actually perform actions. Computer Use is a cutting-edge capability that allows AI models to identify screen content through screenshots and simulate mouse clicks, keyboard input, and other operations to directly control the computer interface — essentially transforming AI into an automated agent that can "see" and "operate" the screen. This technology relies on multimodal visual understanding capabilities, where the AI needs to understand the position and meaning of GUI elements, then generate precise coordinates and operation instructions. The Chrome plugin enables AI to open browsers, navigate web pages, and extract page information — effectively giving AI the ability to browse the internet. The GitHub plugin implements repository browsing, Issue management, Pull Request operations, and other features through the GitHub API, directly integrating code collaboration workflows into the AI workflow.

For developers who rely on custom API access, this feature directly determines Codex's practical usability.

Force-Installing Plugins

Codex++ includes a built-in plugin marketplace entry point that supports force-installing the following commonly used plugins:

• Computer Use: Lets AI directly control the computer interface, performing clicks, typing, and other operations
• Chrome Plugin: Deep integration with the browser, enabling web browsing and information extraction
• GitHub Plugin: Direct interaction with GitHub repositories for code management operations

These plugins are completely unavailable in the original API mode. Codex++'s force-install mechanism brings them back into the developer's toolbox.

Codex++ Installation and Usage Guide

The installation process for Codex++ is very straightforward — almost a one-click setup.

Windows Installation Steps

# 1. Clone the project locally
git clone https://github.com/anthropics/codex-plus-plus

# 2. Enter the project directory and run the batch file
setup.bat

# 3. Select 1 (Install) to complete the installation

After installation, a Codex++ shortcut icon will appear on your desktop.

macOS Installation Steps

macOS users can refer to the instructions in the project README — installation similarly requires just a single command.

Usage Notes

• Close the original Codex process: Before launching Codex++, make sure to quit all running Codex-related processes
• Run as administrator: Since Codex++ needs to dynamically patch the original application files, it's recommended to launch with administrator privileges to avoid patch failures due to insufficient permissions
• Verify the version after launch: Once opened, you can check the Codex++ version number and feature list in the interface to confirm that enhanced features have loaded correctly

Technical Principles: Runtime Dynamic Patching

Codex++ doesn't replace the original Codex — instead, it works through Runtime Patching. At startup, it intercepts and modifies specific logic in the Codex application, removing plugin restrictions in API mode while injecting additional functional modules like session management.

From a technical implementation perspective, the Codex desktop app is built on the Electron framework. Electron is a framework for building cross-platform desktop applications using web technologies (HTML, CSS, JavaScript) — well-known applications like VS Code, Slack, and Discord all use this technology stack. An Electron app's business logic is packaged as JavaScript within ASAR (Atom Shell Archive) archive files. Codex++ works by unpacking these ASAR files at startup, locating the code segments that control plugin permission checks and session management, modifying key logic through AST (Abstract Syntax Tree) manipulation or string replacement — for example, changing the plugin availability check in API mode from false to true — then repacking and loading the modified application. This approach is similar to how browser extensions modify web pages: non-invasive, reversible, and capable of quickly adapting to updates of the original version.

This technical approach brings several practical benefits:

• It doesn't compromise the integrity of the original application — uninstalling restores everything to its original state
• After official Codex updates, Codex++ can quickly adapt to the new version
• Users can freely switch between the original and enhanced versions at any time

The Value and Risks of Community-Driven Models

The "community enhancement of official products" model that Codex++ represents is very common in the AI tools ecosystem. Similar projects include Continue (which adds AI features to VS Code), various community plugins that enhance Obsidian's AI capabilities, and more. This model emerges for deep-seated reasons: AI products iterate at extreme speed, and official teams tend to prioritize core model capabilities and commercialization features, while UX-level details are easily overlooked. Community developers, as power users of the product, can most acutely perceive pain points and respond quickly.

However, such projects also face potential risks — the official team may block patching entry points in subsequent versions, or directly incorporate community features into the official version, rendering third-party tools obsolete. Additionally, since runtime modification of the original application is involved, users should also be mindful of security concerns. It's recommended to only obtain code from the official GitHub repository and avoid using modified versions from unknown sources.

Conclusion

Codex++ is a textbook example of a community-driven enhancement tool — where the official product has functional gaps, community developers quickly step in. The problems it solves aren't revolutionary, but every improvement hits a real pain point for Codex users: chaotic session management, plugins unavailable in API mode, and missing export functionality.

For developers who heavily use OpenAI Codex — especially those who rely on API mode but also need plugin capabilities — Codex++ is practically a must-install tool. The project is still rapidly iterating, and interested developers can follow the project on GitHub for updates and are welcome to contribute code.