Skip to content
50% off Pro: $19.50 onceCODEXUSE50
CodexUse

CodexUse updates and installers: what to expect

UpdatesUpdated September 2026 · 5 min read

CodexUse ships platform packages and a signed, notarized macOS updater. On macOS, updates apply with one in-app restart.

How updates flow

  • Apple Silicon macOS builds check GitHub and download updates in the background.
  • Automatic updates are disabled on Windows while its automatic update path is unreliable. Download the newer Windows package and install it over the old one; your accounts and settings stay in %APPDATA%\codexuse-desktop.
  • When a build is ready, an in-app card offers Restart or Later.
  • Click Later and the card hides for the session. Restart when you are ready to apply the update.
  • The next start shows a toast with the previous and current versions.
Tip: Updates do not run while the app is closed. Restart when you are ready to apply the update.
Homebrew note: If you installed CodexUse with Homebrew, update it with brew update and brew upgrade --cask codexuse. The in-app restart updater is for direct app installs, not Homebrew-managed copies.

Important upgrade note for older installs

On CodexUse 2.5.8 or older? Redownload the current app once and replace the old install. Those builds run the pre-3.x updater, so they do not jump cleanly onto the current release line in place. One manual reinstall and you are back on the auto-update path.

Download links

  • macOS Apple Silicon: stable-macos-arm64-CodexUse.dmg, or install with Homebrew.
  • Windows 11 x64: win-x64-CodexUse-Setup.zip. Windows on ARM installs the same package and runs it under emulation.
  • Linux x64: linux-x64-CodexUse-Setup.tar.gz. Linux arm64: linux-arm64-CodexUse-Setup.tar.gz. Both need GTK and WebKitGTK 4.1, and are tested on Ubuntu 24.04.
  • Intel Mac desktop: not shipped in the current release line.
  • Homebrew: brew install --cask hweihwang/codexuse/codexuse.

Offline behavior

  • The UI and history stay local, but Codex CLI usage still needs internet.
  • License activation and update downloads need connectivity. Offline, the app keeps running on the current build.

What to do if a restart is inconvenient

  • Click Later to keep working, then restart when you are ready.
  • Mid-task, quit CodexUse and reopen it later to apply the update.
  • If a firewall blocked auto-update, download the latest installer manually from the releases page.

Why is a restart required?

CodexUse updates the desktop shell and local background services together. Restarting ensures the new build and bundled runtime pieces start from a clean state. You choose when to restart.

Does the updater change my accounts or settings?

No. Updates replace the app binary and preserve your existing local accounts and settings.

Is there a headless update mode?

No. The app always shows the restart notice. If you want to control timing, download the installer manually and run it when you choose.

What if I installed with Homebrew?

Use brew update and brew upgrade --cask codexuse. Do not use the in-app restart updater on a Homebrew-managed install.

What if I am on Windows, Linux, or an Intel Mac?

Homebrew is a macOS package manager, so the cask covers the Apple Silicon macOS package only. On Windows or Linux, download that platform's package from the same GitHub release; on an Intel Mac, install the optional codexuse-cli npm package (Node.js 22.13 or later) instead — see the CLI reference for requirements and commands.