Update Homebrew cask install command#1189
Conversation
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Updates installation instructions to use the standard Homebrew cask name instead of a custom tap, simplifying setup for users.
Changes:
- Replace
brew install --cask steipete/tap/codexbarwithbrew install --cask codexbar
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ### Homebrew | ||
| ```bash | ||
| brew install --cask steipete/tap/codexbar | ||
| brew install --cask codexbar |
|
Codex review: needs maintainer review before merge. Reviewed May 28, 2026, 10:50 AM ET / 14:50 UTC. Summary Reproducibility: not applicable. this is a docs-only install-command update, not a reported runtime bug. The command target was checked against the current Homebrew cask metadata and upstream PR state. Review metrics: none identified. Merge readiness Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch. Rank-up moves:
Risk before merge
Maintainer options:
Next step before merge
Security Review detailsBest possible solution: Merge the README command update once maintainers are comfortable with the official Homebrew cask path, then handle broader site, badge, and in-app update-message alignment separately if desired. Do we have a high-confidence way to reproduce the issue? Not applicable: this is a docs-only install-command update, not a reported runtime bug. The command target was checked against the current Homebrew cask metadata and upstream PR state. Is this the best way to solve the issue? Yes for the README: after the upstream cask removed the Intel arch gate, replacing the custom tap command with the official cask is the narrow maintainable fix. Broader public-site and badge alignment can be a follow-up rather than a blocker for this one-line README change. AGENTS.md: found and applied where relevant. Codex review notes: model gpt-5.5, reasoning high; reviewed against 857f4fa4aa59. Label changesLabel changes:
Label justifications:
Evidence reviewedWhat I checked:
Likely related people:
What the crustacean ranks mean
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics. How this review workflow works
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 08a7ef4a9a
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| ### Homebrew | ||
| ```bash | ||
| brew install --cask steipete/tap/codexbar | ||
| brew install --cask codexbar |
There was a problem hiding this comment.
For Intel users on macOS 14+, this new command resolves to the Homebrew/homebrew-cask codexbar cask, whose current metadata has depends_on arch: :arm64; Homebrew will reject the install before downloading the universal release. The previous tap cask does not declare that arm64-only constraint, so this README change removes the only Homebrew install path that works for Intel Macs despite the Requirements section still saying only macOS 14+ is needed.
Useful? React with 👍 / 👎.
clawsweeper
Bot
added
rating: 🧂 unranked krab
|
@copilot I opened a Homebrew/homebrew-cask PR to fix that here: I also verified this on an Intel Mac:
Both |
|
To use Codex here, create a Codex account and connect to github. |
| ### Homebrew | ||
| ```bash | ||
| brew install --cask steipete/tap/codexbar | ||
| brew install --cask codexbar |
|
@clawsweeper re-review Upstream Homebrew blocker looks resolved now:
Please re-check whether this README command update is now mergeable, and whether any adjacent docs still need to distinguish GitHub Releases vs Homebrew. |
|
🦞🧹 I asked ClawSweeper to review this item again. Re-review progress:
|
clawsweeper
Bot
added
proof: sufficient
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 666a77ec30
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ### Homebrew | ||
| ```bash | ||
| brew install --cask steipete/tap/codexbar | ||
| brew install --cask codexbar |
There was a problem hiding this comment.
When users follow this new install command, Homebrew installs still disable Sparkle and the app’s About/update hint in Sources/CodexBar/CodexbarApp.swift:320 tells them to run brew upgrade --cask steipete/tap/codexbar. That no longer matches the cask they installed from this README path, so official-cask users are sent to a different tap/token for updates unless the in-app Homebrew guidance is updated at the same time.
Useful? React with 👍 / 👎.
Summary
Context
Verification
Docs-only change; build/tests not run.