Document Homebrew install for the Warp Agent CLI - #524
Conversation
Add a Homebrew tab to the Warp Agent CLI quickstart install step and split the "Automatic updates" section by install method. The `warp-agent-cli` cask is now in the main homebrew/cask repository (macOS 14+ and Linux), so `brew install --cask warp-agent-cli` works without tapping. Homebrew installs are deliberately documented as a secondary option: the client detects them and only *checks* for new versions, surfacing "update available - run brew upgrade --cask warp-agent-cli" instead of staging the update itself. The install script remains the recommended path because it is the only one that self-updates. Co-Authored-By: Warp Agent <agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
This PR was generated with Warp.   |
|
I'm starting a first review of this pull request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
![oz-for-oss[bot]](https://avatars.githubusercontent.com/in/3450139?s=60&v=4){kind=small}
There was a problem hiding this comment.
Overview
This PR documents Homebrew as a secondary installation method for the Warp Agent CLI and updates the automatic-update guidance to distinguish install-script self-updates from Homebrew-managed upgrades. The changed MDX follows the docs structure and the new commands, links, and callout are scoped to the edited pages.
Concerns
- None.
Verdict
Found: 0 critical, 0 important, 0 suggestions
Approve
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
1 participant
What
Documents
brew install --cask warp-agent-clias a secondary install method for the Warp Agent CLI, and clarifies that auto-update behavior differs by install method.agents/cli/quickstart.mdx— adds a Homebrew tab (third, after macOS/Linux and Windows) with a:::cautionthat Homebrew installs don't self-update.agents/cli/index.mdx— splits Automatic updates into two bullets: install script (self-updating) vs. Homebrew (check-only,brew upgrade --cask warp-agent-cli).Why
The
warp-agent-clicask is now in the main homebrew/cask repository (macOS 14+ and Linux,autobump: true), sobrew install --cask warp-agent-cliworks with no tap. It was undocumented.It's documented as secondary on purpose. The client already treats Homebrew installs differently —
crates/warp_tui/src/autoupdate.rsdetects a Caskroom path and takes theAutoupdateEligibility::Homebrewbranch, which only checks for new versions and surfaces:Native install-script installs get real background staging. So the docs now match the shipped behavior rather than the previous blanket claim that "the CLI updates automatically."
Competitive precedent
Every peer that ships a brew cask keeps it out of the primary install path:
curl … | bash; Homebrew is tab 2 of 3 in docs with an explicit "Homebrew installations do not auto-update" callout.npm i -g @openai/codexon openai.com/codex; Homebrew is tab 4 of 4 in the developer docs.cursor-clicask in brew core but doesn't mention brew on the marketing site or in its install docs.Validation
npm run build— 364 pages built, no errors.python3 .agents/skills/style_lint/style_lint.py --changed— no new issues beyond a pre-existing-styleUNRECOGNIZED-TERMwarning for the bolded**Homebrew**list term, which matches the existing**Linux**/**Windows**warnings in the same file.