Inspiration
codex123 grew out of a practical Codex workflow problem: developers want to use relay or third-party compatible model providers while keeping the official ChatGPT login state and the external Codex experience intact.
What it does
codex123 is an unofficial macOS Apple Silicon launcher and manager for the Codex desktop app. It preserves the official ChatGPT login state where possible, manages relay/provider configuration, adds diagnostics, supports external enhancement injection through Chromium DevTools Protocol, and improves script/plugin workflows without modifying the original Codex app files or app.asar.
For OpenAI Build Week, I extended the script market reliability path in v0.2.23. The new release uses a system-proxy-aware request client, adds explicit timeouts and bounded retries, saves the latest valid script market manifest for offline fallback, and adds a reload flow so newly enabled scripts can be applied to the current Codex session when possible.
How I built it
The project uses Rust for the launcher and core logic, Tauri plus React for the manager UI, and a local bridge for Codex enhancement injection. The Build Week work touched the Rust script-market client, Tauri commands, and the manager interface.
I used Codex with GPT-5.6 to inspect the existing Rust/Tauri/React code paths, choose the reliability strategy, implement the script-market changes, update the user-facing flow, and validate the result with formatting, frontend type checks, focused Rust tests, and release checks.
Challenges
The main challenge was making a network-dependent script market more dependable without turning temporary failures into confusing user states. The solution was not just a longer timeout: it combines system proxy support, bounded retries, a last-known-good manifest cache, and explicit reload/restart guidance.
What I learned
For developer tools, reliability is a product feature. A small workflow improvement is much more useful when it has clear fallback behavior, visible state, and a test build that judges can try without rebuilding from source.
What's next
The next steps are improving the visual demo path, adding more regression coverage around script reload behavior, and continuing to keep codex123 scoped to external Codex enhancement without modifying official app files.
Log in or sign up for Devpost to join the conversation.