Claude-Codex-Pro-Tool

# Tool List <p align="center"> <img src="docs/images/claude-codex-pro.png" alt="Claude Codex Pro Tool Icon" width="160"> </p> <p align="center"> English | <a href="README_EN.md">English</a> </p> <p align="center"> <img alt="Release" src="https://img.shields.io/github/v/release/DamonZS/Claude-Codex-Pro-Tool"> <img alt="Stars" src="https://img.shields.io/github/stars/DamonZS/Claude-Codex-Pro-Tool"> <img alt="License" src="https://img.shields.io/github/license/DamonZS/Claude-Codex-Pro-Tool"> <img alt="Rust" src="https://img.shields.io/badge/rust-1.85%2B-orange"> <img alt="Tauri" src="https://img.shields.io/badge/tauri-2.x-24C8DB"> </p> Turn Codex App and Claude Desktop into a fully functional, maintainable, and scalable local AI workstation. Claude Codex Pro Tool is more than just a launcher. It integrates Codex enhancements, Claude Desktop local integration, vendor/relay switching, plugin center, Ponytail, multi-tool Skills, session repair, Pangu memory, script market, prompt optimization, Zed Remote, automatic update, and installation maintenance into a single Tauri operation and maintenance console. You can think of it as providing a local control room for Codex and Claude Desktop, concentrating the capabilities scattered in configuration files, command lines, plugin directories, and script markets. The only repository address: <https://github.com/DamonZS/Claude-Codex-Pro-Tool> ## Suitable for - Those who want to enhance Codex App with more complete local capabilities. - Those who need to switch between multiple API relays and compatible OpenAI protocol vendors. - Those who want to manage Claude Desktop, Claude Code, Codex, MCP, Skills, and plugins in one interface. - Those who frequently repair sessions, export history, switch projects, and manage scripts and plugins. - Those who want verifiable and real functionality, not just seemingly implemented features. ## Core Principles - Local priority: configuration, memory, plugin records, logs, and backups are prioritized locally. - Verifiable: before installing plugins, writing MCP, trusting hooks, and modifying configurations, show commands or diff. - Rollback: before writing key configurations, try to back up; Claude Chinese resource patches provide a restore entry. - No silent trust in third parties: Ponytail/Codex hooks need separate review and trust. - No capability disguise: features that cannot be automatically installed or require manual confirmation are clearly marked for review. ## Download Download the latest version from [GitHub Releases](https://github.com/DamonZS/Claude-Codex-Pro-Tool/releases): - Windows: `claude-codex-pro-*-windows-x64-setup.exe` - macOS Intel: `claude-codex-pro-*-macos-x64.dmg` - macOS Apple Silicon: `claude-codex-pro-*-macos-arm64.dmg` After installation, there are two entries: - `Claude Codex Pro`: a silent launcher used to start Codex and load enhancements. - `Claude Codex Pro Management Tool`: an operation and maintenance console used to manage Codex, Claude, vendors, plugins, scripts, memory, logs, installation maintenance, and updates. The Windows installation package creates desktop and start menu shortcuts. The macOS DMG package contains `Claude Codex Pro.app` and `Claude Codex Pro Management Tool.app`. ## Function Overview ### 1. Codex Launch and Enhancement - Launch Codex through an external launcher. - Automatically handle CDP/helper connections. - Inject a top status indicator into the Codex page. - Support Codex plugin entry unlocking and plugin market entry unlocking. - Support Codex plugin installation channel adaptation, including new `vscode://codex/list-plugins`, `vscode://codex/plugin/install`, and other requests. - Support model whitelist unlocking. - Support service level control entry. - Support image override configuration. - Support session scrolling position recovery. - Support session timeline and session view enhancements. - Support native menu position adjustment. - Support Codex Goals configuration writing. - Support Computer Use Guard to reduce dangerous automation mis-triggering. ### 2. Codex Session Management and Repair - List local Codex sessions. - Delete local sessions. - Export Markdown. - Move project ownership. - View session database location. - Detect new `~/.codex/sqlite/*.db` and old `~/.codex/state_5.sqlite`. - Provider Sync: repair historical session visibility after switching vendors. - Support refilling vendor configuration from the current configuration to avoid overwriting old configurations when switching. ### 3. Vendor and Relay Configuration - Support official mode, official hybrid API mode, and pure API mode. - Support Responses and Chat Completions protocols. - Support multiple vendor profiles. - Support Base URL, API Key, model, User-Agent, context window, and automatic compression threshold. - Support public configuration and context configuration splitting. - Support MCP/Skills/Plugins context selection. - Support refilling configuration from current `~/.codex/config.toml` and `auth.json`. - Support testing vendor connectivity. - Support clearing API mode and returning to official login configuration. - Support compatible API/relay station configuration, such as self-built services or third-party relays. Example configuration will be written to `~/.codex/config.toml`: ```toml model_provider = "custom" [model_providers.custom] name = "custom" wire_api = "responses" requires_openai_auth = true base_url = "https://example.com/v1" experimental_bearer_token = "sk-..." ``` ### 4. Claude Desktop Management - Launch official Claude Desktop. - Focus on Claude Desktop window. - Open Claude Desktop DevTools. - Create a new Claude Desktop conversation. - Paste drafts into Claude Desktop. - Submit text to Claude Desktop. - Detect Claude Desktop installation location, process status, and integrity status. - Display official MSIX/CDP blocking diagnosis, without disguising as injected. ### 5. Claude Chinese Capability The project provides two types of Chinese paths, suitable for different risk preferences: - Claude Chinese package window: independently load `https://claude.ai/new` in WebView, inject Chinese override scripts and top status indicators during creation. Recommended to use this method first, without modifying official installation files. - Claude Desktop Chinese resource patch: an optional local resource patch, refer to `Jyy1529/claude-desktop_win-zh_cn` public resources, write `zh-CN.json`, locale configuration, and necessary frontend language support patches. Backup before execution, and the management tool provides a restore entry. Note: Official Claude Desktop's MSIX, signature, and integrity mechanism may limit direct DOM injection or file patches. Packaging windows are a low-risk solution; resource patches are user-explicit local modification solutions. ### 6. Plugin Center The plugin center unifies multiple sources into a directory view: - Claude official plugin market. - Claude Desktop MCP configuration items. - GitHub MCP Registry. - Awesome Claude Code resources. - OpenAI Codex Plugins repository. - Ponytail multi-tool plugins. - Identifiable Skill bundles. - Community resource links. Each entry will display: - Source, category, author, license. - Installation status. - Risk prompts. - Dependency requirements. - Installation command preview. - Configuration diff. - Installation, uninstallation, open source, and other operations. Installation strategy: - Official Claude plugins through `claude plugin marketplace add/install`. - Claude Desktop MCP write `claude_desktop_config.json`, backup before writing. - Codex plugins through `codex plugin marketplace add/list/add`. - Skill bundles only install if the structure is recognizable. - Unknown community MCP only display by default, do not automatically execute scripts. ### 7. Ponytail Integration Integrated [DietrichGebert/ponytail](https://github.com/DietrichGebert/ponytail), support multi-tool installation: - Ponytail for Codex: call Codex CLI to add marketplace, install `ponytail@ponytail`. - Ponytail Codex hooks: preview hooks to be trusted, users confirm before writing trust status. - Ponytail Skills for Codex: copy Ponytail Skills to Codex skills directory, backup before overwriting. - Ponytail for Claude Code: install through Claude Code CLI. - Ponytail MCP for Claude Desktop: write Claude Desktop MCP configuration. - Ponytail Organization Plugin for Claude Desktop: write Claude Desktop development mode readable organization plugin directory. - Ponytail MCPB: generate `.mcpb` installation package and submit to Claude Desktop official confirmation process. - Ponytail for GitHub Copilot CLI: install through Copilot CLI plugin system. Claude Desktop's local plugin package process does not require Claude CLI login: it configures development mode, writes Codex/Ponytail MCP, and copies Ponytail skills to the organization plugin directory. ### 8. Codex OpenAI Plugin Repository - Download OpenAI official `openai/plugins` repository zip. - Limit download size. - Safe decompression, prevent zip path traversal. - Verify `.agents/plugins/marketplace.json`. - Verify each plugin directory's `.codex-plugin/plugin.json`. - Register to `~/.codex/config.toml` `[marketplaces.openai-curated]`. - Display specific failure reasons when errors occur, do not register bad repositories as successful. ### 9. Pangu Memory Pangu memory uses SQLite, without introducing cloud-side embedding or external vector libraries. Support: - Manual writing of long-term memory. - Automatic generation of memory to be confirmed. - User confirmation before entering long-term memory. - Workspace isolation. - `global` global memory. - Current workspace + global mixed query. - Keyword normalization and lightweight similarity sorting. - Update access times and last access time after hitting. - Key desensitization, avoid API key, Bearer token, `sk-` class content original入库. - Self-inspection and repair. - Export JSON. - Import JSON, support merging or replacing. Default database: ```text ~/.claude-codex-pro/memory_assist.sqlite ``` ### 10. Script Market and User Scripts - Refresh script market. - Download and install scripts. - Manage local user scripts. - Enable/disable individual scripts. - Delete user scripts. - Build enabled script bundles. - Inject script extensions into frontend capabilities through Codex. ### 11. Prompt Optimizer Integrated [linshenkx/prompt-optimizer](https://github.com/linshenkx/prompt-optimizer) prompt optimization workflow. Support: - Open prompt optimization page within the management tool. - Independent prompt optimization window. - Use as part of the tool system, no additional pop-up control window. ### 12. Zed Remote - Identify Zed installation path. - Parse SSH host, user, port. - Parse remote projects from Codex global state and thread context. - Maintain recent remote project registry. - Construct `zed://ssh/...` remote open links. - Support default open, reuse window, new window, append to current window, and other strategies. - Support forgetting remote projects. ### 13. Upstream Worktree - Read Git remote, branch, worktree list. - Create worktree from the latest remote tracking branch. - Support local and remote projects. - Verify branch name and base branch. - Avoid deriving task branches from expired local HEAD. ### 14. Watcher and Self-Recovery - Install watcher on Windows. - Detect Codex process and CDP port status. - Recover invalid launcher. - Support enabling, disabling, installation, uninstallation. - Support stopping launcher/Codex related processes. ### 15. Installation Maintenance and Update - Installation entry. - Uninstallation entry. - Repair shortcuts. - Repair backend configuration. - Check updates. - Download Release assets. - Launch installer. - Read latest logs. - Copy diagnostic information. - Reset settings. - Reset image override settings. ### 16. Automatic Build and Release - `Auto release installers`: automatically calculate `V0.01` series version, create tag, build Windows installation package, macOS x64 DMG, macOS arm64 DMG, and upload `latest.json` after main push or manual trigger. - `PR build artifacts`: used for PR and daily build verification. - `release-assets`: reserved for manual GitHub Release use. Automatic version increment rule: ```text V0.01 -> V0.02 -> ... -> V0.99 -> V1.00 ``` ## Management Tool Pages - Overview: running status, Codex/Claude quick actions, log summary, official relay station entry. - Vendor: manage Codex API/relay/official hybrid configuration. - Tools and plugins: session management, historical session repair, plugin center, Ponytail, Codex plugin repository, Claude Desktop local plugins, Pangu memory. - Prompts: prompt optimizer. - Scripts: script market and user script management. - Settings: real available switches, startup parameters, enhancement matrix, memory, Zed, watcher, installation maintenance. ## Security Boundary - Do not silently modify Claude Desktop private plugin library. - Do not silently trust third-party hooks. - Do not automatically execute unknown community MCP installation scripts. - Do not write API key, Bearer token, or complete authentication configuration into ordinary logs. - Do not execute third-party GitHub content as trusted code by default. - Claude Chinese package window does not modify official Claude Desktop files. - Claude Desktop Chinese resource patch belongs to user-explicit local modification solutions, backup before execution, and can be restored. ## Data Location - Codex configuration: `~/.codex/config.toml` - Codex login status: `~/.codex/auth.json` - Codex database: prioritize `~/.codex/sqlite/*.db`, fallback to old `~/.codex/state_5.sqlite` - Codex plugin repository cache: `~/.codex/.tmp/plugins` - Codex skills: `~/.codex/skills` - Claude Desktop MCP configuration: Windows usually `%APPDATA%\Claude\claude_desktop_config.json` - Claude Desktop 3P configuration: Windows usually `%LOCALAPPDATA%\Claude-3p` - Claude Codex Pro status: `~/.claude-codex-pro/` - Memory database: `~/.claude-codex-pro/memory_assist.sqlite` - Provider Sync backup: `~/.codex/backups_state/provider-sync` ## FAQ ### Why does a commit show two Actions? Because the current repository has two workflows listening to `main` push: - `Auto release installers`: build and release installation packages. - `PR build artifacts`: daily build verification. This is not releasing two versions, just the same commit triggers two pipelines. ### Why only source code in Release? If the installation package build job succeeds but the release job fails, the GitHub page will only display the automatically generated source code zip/tar.gz. Need to check `Auto release installers` `Publish release and latest.json` step. The current workflow will first release draft release, then generate and upload `latest.json`, to avoid draft release cannot be queried by tag and cause failure. ### Codex does not show enhancement indicators? Confirm to start Codex from `Claude Codex Pro` entry, not directly start the original Codex. If still not displayed, open the management tool to view diagnosis and logs, focus on checking helper port, CDP connection, and `renderer.script_loaded` records. ### Claude does not become Chinese? Prioritize using `Open Chinese Window`. This is an independent WebView package window, not the official Claude Desktop original window. If using resource patches, confirm Claude Desktop has completely exited, installation directory is writable, and view patch status or execute restore on failure. ### Plugin installation fails? First open installation preview, confirm installation type: - Claude official plugins require `claude` CLI. - Claude Desktop MCP requires writing `claude_desktop_config.json`. - Claude Desktop local organization plugins require development mode and directory write permissions. - Codex plugins require `codex` CLI. - Ponytail hooks require separate review and trust. - Community MCP and Skill require recognizable structure. ### macOS prompts application cannot open or damaged? Unsigned or un notarized builds may be intercepted by Gatekeeper. Can allow opening in “System Preferences -> Privacy and Security”. If still prompts damaged, can execute: ```bash sudo xattr -rd com.apple.quarantine /Applications/Claude\ Codex\ Pro.app sudo xattr -rd com.apple.quarantine /Applications/Claude\ Codex\ Pro\ 管理工具.app ``` ### Does support Intel Mac? Support. Release will provide `macos-x64.dmg` and `macos-arm64.dmg` separately. Intel Mac uses x64 package, Apple Silicon uses arm64 package. ## Build and Development This project is a Rust workspace + Tauri management tool + Vite/React frontend. The `package.json` in the repository root comes from the upstream structure and is not used to build this project; actual frontend dependencies are installed and built under `apps/claude-codex-pro-manager`. ### Environment Requirements - Git. - Node.js 22 or higher. - npm. - Rust stable toolchain, including `cargo`, `rustc`, `rustfmt`. - Windows build requires Visual Studio Build Tools / MSVC C++ toolchain. - Windows installation package requires NSIS. - macOS build requires Xcode Command Line Tools. - macOS DMG creation uses built-in `sips`, `iconutil`, `codesign`, `hdiutil`. Windows NSIS installation example: ```powershell choco install nsis -y ``` macOS Rust target installation example: ```bash rustup target add x86_64-apple-darwin rustup target add aarch64-apple-darwin ``` ### Install Dependencies ```bash cd apps/claude-codex-pro-manager npm install --package-lock=false cd ../.. ``` If you want to strictly use lockfile, you can replace the first command with `npm ci`. CI currently uses `npm install --package-lock=false`. ### Local Development Startup ```bash cd apps/claude-codex-pro-manager npm run dev ``` This command will start the management tool by Tauri CLI and automatically run the Vite development server. Vite listens to: ```text http://localhost:1420 ``` If you only want to debug the frontend page, you can run: ```bash cd apps/claude-codex-pro-manager npm run vite:dev ``` Normal browser preview does not have Tauri backend, involving system configuration, process, plugin installation, Claude Chineseization and other buttons will return preview or cannot be executed; real functionality please use `npm run dev` to start Tauri application verification. ### Local Verification Before submitting, it is recommended to run: ```bash npm --prefix apps/claude-codex-pro-manager run check npm --prefix apps/claude-codex-pro-manager run vite:build cargo fmt --check cargo test --workspace cargo build --release ``` Common directional verification: ```bash cargo test -p claude-codex-pro-core --manifest-path Cargo.toml plugin_hub -- --nocapture cargo test -p claude-codex-pro-core --manifest-path Cargo.toml memory_assist -- --nocapture cargo test -p claude-codex-pro-core --manifest-path Cargo.toml relay_config -- --nocapture cargo test -p claude-codex-pro-manager --manifest-path Cargo.toml --test windows_subsystem -- --nocapture ``` ### Production Binary ```bash npm --prefix apps/claude-codex-pro-manager run vite:build cargo build --release ``` Main products: ```text target/release/claude-codex-pro.exe target/release/claude-codex-pro-manager.exe ``` On macOS or Linux, there is no `.exe` suffix: ```text target/release/claude-codex-pro target/release/claude-codex-pro-manager ``` You can also run in the management tool directory: ```bash cd apps/claude-codex-pro-manager npm run build ``` This script will first build the silent launcher and then execute `tauri build`. The current official installation package still uses NSIS / DMG scripts in the repository. ### Windows Installation Package ```powershell npm --prefix apps/claude-codex-pro-manager install --package-lock=false npm --prefix apps/claude-codex-pro-manager run check npm --prefix apps/claude-codex-pro-manager run vite:build cargo test --workspace cargo build --release New-Item -ItemType Directory -Force dist/windows/app | Out-Null Copy-Item target/release/claude-codex-pro.exe dist/windows/app/ Copy-Item target/release/claude-codex-pro-manager.exe dist/windows/app/ $version = "1.2.9" $makensis = "${env:ProgramFiles(x86)}\NSIS\makensis.exe" if (-not (Test-Path $makensis)) { $makensis = "makensis" } Push-Location scripts/installer/windows & $makensis "/INPUTCHARSET" "UTF8" "/DVERSION=$version" ClaudeCodexPro.nsi Pop-Location ``` Output: ```text dist/windows/claude-codex-pro-1.2.9-windows-x64-setup.exe ``` ### macOS DMG Apple Silicon: ```bash npm --prefix apps/claude-codex-pro-manager install --package-lock=false npm --prefix apps/claude-codex-pro-manager run vite:build rustup target add aarch64-apple-darwin cargo build --release --target aarch64-apple-darwin BINARY_DIR="$PWD/target/aarch64-apple-darwin/release" bash scripts/installer/macos/package-dmg.sh 1.2.9 arm64 ``` Intel Mac: ```bash npm --prefix apps/claude-codex-pro-manager install --package-lock=false npm --prefix apps/claude-codex-pro-manager run vite:build rustup target add x86_64-apple-darwin cargo build --release --target x86_64-apple-darwin BINARY_DIR="$PWD/target/x86_64-apple-darwin/release" bash scripts/installer/macos/package-dmg.sh 1.2.9 x64 ``` Output: ```text dist/macos/claude-codex-pro-1.2.9-macos-arm64.dmg dist/macos/claude-codex-pro-1.2.9-macos-x64.dmg ``` Local scripts use ad-hoc codesign, not Apple Developer ID signature or notarization. Therefore, local DMG may be prompted by Gatekeeper, please manually allow according to the above macOS FAQ. ## GitHub Actions Main workflows: - `.github/workflows/auto-release-installers.yml`: Automatically release after main push or manual trigger. - `.github/workflows/pr-build.yml`: Build verification products during PR, main push, and manual trigger. - `.github/workflows/release-assets.yml`: Reserved for manual GitHub Release. Automatic release process: 1. Push to `main` or manually run `Auto release installers`. 2. `scripts/release/next-release-tag.js` reads existing tags. 3. Generate the next version `V0.01` series tag. 4. Create tag and draft Release. 5. Windows runner builds `.exe` installation package. 6. macOS Intel runner builds x64 DMG. 7. macOS Apple Silicon runner builds arm64 DMG. 8. Upload installation packages. 9. Release Release. 10. Generate and upload `latest.json`. Automatic release product example: ```text claude-codex-pro-0.01-windows-x64-setup.exe claude-codex-pro-0.01-macos-x64.dmg claude-codex-pro-0.01-macos-arm64.dmg latest.json ``` ## Project Structure ```text apps/ claude-codex-pro-launcher/ Silent launcher claude-codex-pro-manager/ Tauri management tool assets/inject/ renderer-inject.js Codex enhancement script claude-chinese-inject.js Claude Chinese packaging window script crates/ claude-codex-pro-core/ Startup, injection, configuration, plugin, update, installation, bridge claude-codex-pro-data/ Session data, export, Provider Sync scripts/installer/ windows/ClaudeCodexPro.nsi Windows NSIS installer macos/package-dmg.sh macOS DMG packaging script docs/ code-knowledge-graph.md Code knowledge graph full-code-review.md Full code review record ``` ## Feedback - Issues: <https://github.com/DamonZS/Claude-Codex-Pro-Tool/issues> - Discussion group QR code: <https://docs.qq.com/doc/DQ2VOanZTTFZJcUpZ#> ## License and Rules This repository uses a custom source visible restriction protocol, not an OSI certified open-source protocol. Without DamonZS or authorized maintainer written permission, prohibit any modification, release, distribution, renaming, repackaging or hiding the source of this project in any way, including manual modification, AI-assisted modification, script, codemod, batch replacement, automated rewriting, binary patch and metadata rewriting. Author information, repository address, copyright statement, product name, brand, publisher, sponsor or payment identity, protocol and rules files must not be deleted, replaced, hidden or weakened. These restrictions do not constrain DamonZS, repository owners, authorized maintainers, and AI assistants, scripts, CI, codemod, formatting tools or automated tools working under their instructions. Official project subsequent development can continue to use AI and automation capabilities. Authorized maintainer list see [MAINTAINERS.md](MAINTAINERS.md). See [LICENSE](LICENSE) and [RULES.md](RULES.md) for details. ## Description Claude Codex Pro Tool is an external enhancement tool, not an official project of OpenAI, Anthropic, Claude or Codex. After the official application is updated, if the page structure, protocol, CLI, plugin format or configuration path changes, the injection script and adaptation logic of this project may need to be updated synchronously.