• English
  • Codex++

    A non-invasive enhancement launcher for the Codex desktop app (the BigPizzaV3 edition). It leaves official install files untouched, injects enhancements via an external launcher, and ships a management tool that writes third-party providers into ~/.codex/config.toml — exactly what we need for ByteSeek.

    Same name, different project

    This guide covers BigPizzaV3/CodexPlusPlus (launcher + management tool). A same-named project that patches app.asar has a completely different architecture — its configuration does not apply here.

    Install

    The only official release channel is the GitHub Releases page; download the latest installer per platform:

    PlatformInstaller
    WindowsCodexPlusPlus-*-windows-x64-setup.exe from the Releases page
    macOS (Intel)CodexPlusPlus-*-macos-x64.dmg, same page
    macOS (Apple Silicon)CodexPlusPlus-*-macos-arm64.dmg, same page

    After installation you get two entries: Codex++ (launch instead of the original Codex icon) and the Codex++ management tool (providers and enhancements).

    Prerequisites

    • Official Codex desktop app and Codex++ installed
    • An OpenAI-format group key created on the API Keys page

    Add ByteSeek as a provider

    1. Open the management tool → provider settings → add provider.
    2. Fill in:
      • Mode: pure API
      • Name: ByteSeek
      • Base URL: https://tokens.byteseek.ai/v1
      • API Key: your sk- key
      • Upstream protocol: prefer Responses; fall back to Chat Completions on older clients
    3. For model names use exact IDs from the model plaza, e.g. gpt-5.6-sol.
    4. Save and launch from the Codex++ icon. If Codex is already running, quit it first.
    Provider form fields
    FieldValue
    Provider nameYour choice, e.g. ByteSeek
    Base URLhttps://tokens.byteseek.ai/v1
    ProtocolOpenAI-compatible
    API KeyYour sk- key
    ModelModel ID, e.g. gpt-5.6-sol

    After saving, set ByteSeek as the active provider in the list — desktop Codex then routes through ByteSeek.

    Verify

    Launch via Codex++ and start a conversation; a normal reply means success. The request appears on the usage page.

    Common issues

    SymptomFix
    Enhancements not activeYou launched the original Codex icon. Launch via Codex++ so the launcher can inject
    401Invalid or truncated key — re-paste in the management tool
    403Model not in group or format mismatch, see Error Codes
    Config changes not applyingQuit Codex and relaunch via Codex++, or use the restart button
    © 2026 ByteSeek Limited. All rights reserved.TermsPrivacyDisclaimer