CodexUse updates and installers: what to expect
CodexUse uses signed builds and a simple in-app restart prompt. Here is how updates work, how long you can wait, and where to download installers.
How updates flow
- The packaged app checks GitHub for updates and downloads them in the background.
- When a build is ready, you see an in-app card with Restart and Later.
- If you click Later, the card hides for the current session. Restart when you are ready to apply the update.
- On the next launch you get a toast showing the previous and current versions.
Tip: Updates do not run while the app is closed. Restart when you are ready
to apply the update.
Download links
- macOS (Apple Silicon): DMG from the GitHub releases feed linked on the download button.
- Linux (ARM64): AppImage from the same releases feed.
- Windows: in progress. Join the waitlist from the landing page to be notified.
- Homebrew:
brew install --cask hweihwang/codexuse/codexuse.
Offline behavior
- The UI and history are local, but Codex CLI usage still requires internet.
- License activation and update downloads need connectivity. If you are offline, the app keeps running with the current build.
What to do if a restart is inconvenient
- Click Later to keep working, then restart when you are ready.
- If you are in the middle of a long task, quit CodexUse and reopen it later to apply the update.
- You can always download the latest installer manually from the releases page if auto-update was blocked by a firewall.
Why is a restart required?
CodexUse bundles the Codex CLI and background services. Restarting ensures the new build and CLI are loaded together. You choose when to restart.
Does the updater change my profiles or chats?
No. Updates replace the app binary and preserve your existing local profiles, chats, 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.