Codex Patch Studio

Turn your installed Codex desktop app into a version-aware, locally verified developer platform.

Comment

edit: Oh no.

I thought I could edit some of the submission details after the fact. I was running out of time (1 min left lol), so I entered gibberish text for the the conversation ID and possibly something else I can't remember exactly.

Inspiration

Codex is already a capable coding environment, but advanced users often need workflows that do not fit into a single project or a fixed provider setup. I wanted a safe way to experiment with Codex desktop itself without overwriting the signed Store installation, losing chat history, mixing provider credentials, or rebuilding every customization by hand after an update.

What it does

Codex Patch Studio turns the currently installed Windows Codex app into a separate, user-controlled development platform. It discovers and fingerprints the installed Store build, creates a new local clone, applies selected source-only feature modules, verifies the unpacked and repacked result, and switches the launcher only after every check passes.

The patched instance can run beside stock Codex. It keeps its own configuration, Electron profile, caches, and local services while sharing the user's canonical chat sessions and index by default.

The current feature set includes:

  • a lazy catalog shim that exposes thousands of existing chats without eagerly loading full conversation bodies;
  • native settings for providers, model routing, prompt tools, personas, orchestrations, imports, patch management, and feature development;
  • OpenAI, DeepSeek, Z.ai GLM, Qwen/DashScope, Cerebras, Ollama, LM Studio, and custom-provider controls;
  • multi-project orchestration chats and project-specific child chats;
  • import and repair workflows for Augment, Kiro, Roo Code, and Cline history;
  • an extensible feature-module system with version-family adapters, dependency/conflict checks, restricted execution, and packed verification;
  • Off, Notify, and Auto rebuild policies for installed Codex updates, with a last-known-good fallback.

Developer Tools

This is infrastructure for developers who use Codex as an everyday workspace. It combines version-aware patching, local interoperability, model/provider configuration, agent orchestration, chat migration, and verification into one reproducible workflow. The project is designed to fail closed when an application update changes a structural anchor instead of silently producing a broken build.

How we built it

The patcher is implemented with Node.js and PowerShell on Windows 11. Source-only feature manifests describe compatibility, anchors, dependencies, conflicts, local ports, permissions, and verification markers. The builder copies the user's own installed Codex package into a new immutable candidate directory, runs the selected module operations, checks JavaScript syntax and structural receipts, repacks the app, and validates the packed output before changing launcher metadata.

Codex accelerated the work by helping inspect application behavior, compare successive installed builds, model the native chat and settings flows, implement isolated patch modules, reproduce failures, and turn each discovery into an automated contract test. The important design decisions were encoded as fail-closed checks rather than left as manual reverse-engineering notes.

The repository intentionally contains no Codex executables, ASAR archives, extracted proprietary bundles, generated clones, user chats, credentials, or provider keys. Every user builds locally from their own installed Codex copy.

Challenges we ran into

The hardest problem was preserving native behavior across app updates. Minified renderer filenames and implementation details can change, so a simple text replacement is not reliable enough. The final design uses version-family adapters, structural anchor cardinality checks, immutable candidate builds, host-generated verification receipts, and a last-known-good launcher.

Another challenge was making stock and patched Codex coexist. They need separate configuration and Electron state, but users still expect the same projects and chats. The launcher now isolates patched state while linking the canonical sessions and chat database intentionally.

Accomplishments that we're proud of

  • Stock Codex is never edited in place.
  • A failed candidate cannot replace the last verified clone.
  • Stock and patched Codex can run simultaneously with independent provider configuration.
  • The lightweight chat catalog supports up to 10,000 threads while keeping full bodies lazy.
  • The complete source-only test suite currently contains 112 passing tests.
  • A local self-extracting package can be built without publishing the user's installed Codex material.
  • The feature framework supports core, reviewable contribution, and private local modules.

What's next

  • Expand tested adapters as new Codex version families ship.
  • Add more independently packaged community feature modules.
  • Improve judge-friendly demo packaging without crossing the source-distribution boundary.
  • Add automated compatibility reporting from Windows CI runners.
  • Continue reducing startup overhead for very large chat archives.

Built With

Share this project:

Updates