Our Process

We extend the official Codex experience with Windows-focused fixes while keeping version numbers aligned. Here’s how we ship reliable, community-driven releases.

1. Track official releases daily

We monitor upstream Codex every day. When a new official release appears, we pull it into the fork immediately so Windows users are never far behind the mainline experience.

2. Apply Windows fixes and polish

Platform-specific patches address shell quirks, file-path issues, sandbox behaviour, and performance tweaks discovered by the community. Everything lives in the open for review.

3. Validate with automated CI + manual QA

All changes pass automated CI followed by manual QA on real Windows environments. We verify install flows, CLI behaviour, and core workflows before tagging a release.

4. Publish matched-version releases

Once validation passes, we publish a release that matches the official version number with a Windows suffix (for example 0.46.1-win.1). The suffix shows which iteration of the fork you’re running.

Why the fork exists

Deliver a first-class CLI experience on Windows without waiting for upstream changes.
Share community fixes openly so they can inform official updates.
Provide documentation that speaks directly to Windows workflows.

What you can expect from each release

Version number that mirrors the official Codex release, plus a Windows suffix.
Release notes summarising Windows-specific fixes and behavioural changes.
Updated npm package @cpjet64/codex-windows and prebuilt binaries published on the releases page.

How to get involved

Report bugs or suggest improvements on the issue tracker .
Submit pull requests with clear Windows repro steps and testing notes.
Share feedback on installation docs, tooling, or missing coverage in the docs library.

Want real-time updates? Watch the releases feed or follow the fork on GitHub to be notified the moment a matched release goes live.