Remove Homebrew from recommended installation methods or provide an official tap

[apstndb]

URL of the page with the issue

https://geminicli.com/docs/get-started/installation/#install-gemini-cli

What is the problem?

According to docs/get-started/installation.mdx and README.md, Homebrew is listed as one of the recommended installation methods for Gemini CLI.

However, gemini-cli is currently marked as deprecated in homebrew-core, and it does not seem likely that this will be reverted.

Reference: Homebrew/homebrew-core#289444

We don't have a way to make a distinction between the general public and enterprise customers, so we deprecate based on the situation the default user will find themselves in.

Given this situation, the current documentation may be misleading for general users.

What did you expect to happen?

Would you consider one of the following?

• Removing Homebrew from the recommended installation methods
• Providing an official tap for Homebrew users

Additional context

No response

[gemini-cli]

Effort Analysis:
The task requires removing Homebrew installation instructions from docs/get-started/installation.mdx, README.md, docs/resources/uninstall.md, and docs/resources/faq.md. Additionally, it involves updating the getInstallationInfo function in packages/cli/src/utils/installationInfo.ts (specifically the updateMessage for PackageManager.HOMEBREW) to notify existing users of the deprecation. Since the changes are restricted to documentation and a single utility file with straightforward logic, it fits the criteria for effort/small (Documentation & Strings and Localized Bug Fixes).

[alfinohatta]

I think the short-term fix should be removing brew install gemini-cli from docs/get-started/installation.mdx, README.md, and related documentation such as uninstall.md and faq.md so new users are not directed toward a deprecated package.

The getInstallationInfo() logic in packages/cli/src/utils/installationInfo.ts should also be updated so PackageManager.HOMEBREW provides a clear migration message for existing Homebrew users instead of implying that the package is still a recommended installation path.

If Homebrew support is still intended long-term, an official tap would be a better approach because it would decouple Gemini CLI releases from homebrew-core policies and provide a controlled distribution channel. This would keep the installation experience consistent for both new and existing users.