Support standalone Windows installer (`codex-setup.exe`)

### What variant of Codex are you using? App ### What feature would you like to see? Many Windows users cannot easily install applications from the Microsoft Store due to system restrictions, corporate policies, offline environments, or personal preference for traditional installers. Currently the Codex Windows app appears to be distributed only through the Microsoft Store. It would be very helpful if a standalone installer such as `codex-setup.exe` or `.msi` were provided. Benefits of a standalone installer: - Allows installation without Microsoft Store - Works in offline or restricted enterprise environments - Lets users choose the installation directory - Easier automation and deployment (scripts, DevOps, package managers) - Better compatibility with portable setups and custom Windows environments Many developer tools provide both distribution methods (Store + standalone installer), which gives users more flexibility. A simple downloadable installer from the GitHub releases page or official website would solve this. Example: ``` codex-setup.exe codex-x64.msi ``` ### Additional information Other developer tools commonly provide standalone installers alongside store versions, which improves accessibility for developers using custom setups or environments where the Microsoft Store is disabled. Providing a traditional installer would make Codex easier to adopt across a wider range of developer environments.

GitHubToolAISource
0Sign in to voteCopy link

FL score

72

out of 100

Verdict

VALIDATE

high confidence

Competition

No competitor data yet

Trend

No signal yet

Add a standalone Windows installer to Codex to reach users locked out of the Microsoft Store.

The pain

Windows developers in enterprise environments, offline networks, and restricted corporate setups cannot install Codex because their systems block Microsoft Store access. They resort to workarounds, manual builds, or abandon the tool entirely.

The gap

Codex distribution is Microsoft Store-only. Competitors like VS Code, JetBrains tools, and other developer software ship both Store and standalone installers. This creates friction for a meaningful segment of potential users.

Build angle

This is a distribution/packaging feature, not a product innovation. The effort is moderate (build MSI/EXE, host on GitHub releases, maintain two distribution channels). The payoff depends entirely on how many blocked users actually exist and whether they'll switch to Codex once unblocked.

Strengths

  • Solves a real, documented friction point for enterprise and offline users
  • Low technical complexity, standard Windows installer tooling
  • Precedent exists across developer tools (VS Code, Sublime, JetBrains)
  • Enables automation and scripted deployments, which enterprises value
  • GitHub releases distribution requires minimal infrastructure

Risks

  • Unclear market size, how many potential users are actually blocked by Store-only distribution?
  • Maintenance burden increases (two installers, two update paths, potential version drift)
  • Does not address core product adoption barriers; assumes distribution is the primary blocker
  • Enterprise sales typically require dedicated support, not just an installer
  • If user base is small, effort-to-impact ratio is poor

Questions about this idea?

FlyBot reads the scoring and gives you a second opinion on “Support standalone Windows installer (`codex-setup.exe`)”.

Open FlyBot