CodexUse Homebrew install and update guide
If you want the lowest-friction macOS install, Homebrew is the clean path. The official cask installs the desktop app cleanly, and you can add the optional codexuse CLI separately with npm when you want terminal workflows.
Why this path is useful
- One command installs the desktop app cleanly on macOS.
- The cask tracks current releases, so updates fit the rest of your macOS package workflow.
- You can add the CLI separately only on machines that actually need terminal workflows.
Fast fix
Install
brew install --cask hweihwang/codexuse/codexuse
open -a CodexUse
npm install -g codexuse-cli
codexuse --versionUpdate later
brew update
brew upgrade --cask codexusebrew upgrade --cask codexuse, not CodexUse's in-app restart updater. If Homebrew now fails with either App source '/Applications/CodexUse.app' is not there or It seems there is already an App at '/opt/homebrew/Caskroom/.../CodexUse.app', run brew uninstall --cask --force hweihwang/codexuse/codexuse, remove any dangling /Applications/CodexUse.app, then brew install --cask hweihwang/codexuse/codexuse.How to verify the install
brew info --cask hweihwang/codexuse/codexuse
npm list -g codexuse-cli --depth=0
codexuse --versionYou should see CodexUse.app from Homebrew, and if you installed the CLI separately, codexuse --version should resolve too.
What to do after install
- Launch the app once so you can add or switch profiles from the desktop UI.
- If you installed the CLI too, open a new terminal tab if
codexusewas not visible in your current shell yet. - Use the optional CLI for profile switching, sync, and Telegram daemon workflows.
Troubleshooting table
| Symptom | Likely cause | Action |
|---|---|---|
codexuse: command not found right after install |
Your current shell has not picked up the new Homebrew binary yet | Open a fresh terminal tab, then run codexuse --version again |
| The app opens but you are unsure which version is installed | You have not checked the cask metadata | Run brew info --cask hweihwang/codexuse/codexuse |
brew upgrade --cask codexuse fails with App source '/Applications/CodexUse.app' is not there or It seems there is already an App at '/opt/homebrew/Caskroom/.../CodexUse.app' |
Homebrew's app bundle or symlink is out of sync, often after stale cask metadata or an in-app update touched the Homebrew-managed copy | Run brew uninstall --cask --force hweihwang/codexuse/codexuse, remove any dangling /Applications/CodexUse.app, then install again with brew install --cask hweihwang/codexuse/codexuse |
| You need Linux or Intel Mac desktop support too | Homebrew only covers the current Apple Silicon macOS desktop release line | Use codexuse-cli on that machine for terminal workflows, and check the updates guide for the current desktop support line |
What to avoid
- Manually replacing app files when a normal
brew upgradewill do the job. - Using the in-app restart updater on a Homebrew-managed install. Use
brew upgrade --cask codexuseinstead. - Assuming the current shell updates itself after install.
- Using Homebrew instructions as a Linux or Intel Mac desktop install path. The current desktop release line is Apple Silicon macOS only.
Related
What is the Homebrew install command for CodexUse?
Use brew install --cask hweihwang/codexuse/codexuse. That installs CodexUse.app on Apple Silicon macOS. If you want the CLI too, add npm install -g codexuse-cli.
How do I update CodexUse from Homebrew?
Run brew update and then brew upgrade --cask codexuse. Do not use the in-app restart updater on a Homebrew install. If Homebrew fails with either App source '/Applications/CodexUse.app' is not there or It seems there is already an App at '/opt/homebrew/Caskroom/.../CodexUse.app', clear the local record with brew uninstall --cask --force hweihwang/codexuse/codexuse, remove any dangling /Applications/CodexUse.app, then reinstall.
How do I verify the install worked?
Run brew info --cask hweihwang/codexuse/codexuse. If you also installed the CLI separately, run codexuse --version too.