[DOCS] Contradictory/Missing information regarding Auto-updates for Homebrew and WinGet installations

Documentation Type

Unclear/confusing documentation

Documentation Location

• https://code.claude.com/docs/en/quickstart - https://code.claude.com/docs/en/setup - https://code.claude.com/docs/en/overview

Section/Topic

Installation instructions and the "Auto updates" behavior section for third-party package managers.

Current Documentation

• docs/en/setup.md: Under "Auto updates", it states: "Claude Code automatically keeps itself up to date... Homebrew and WinGet installations do not auto-update. Use brew upgrade claude-code or winget upgrade Anthropic.ClaudeCode to update manually."
• docs/en/quickstart.md: Lists Homebrew and WinGet as primary installation methods in "Step 1" but contains no mention of the fact that these versions will not automatically receive security or feature updates.
• docs/en/overview.md: States generally: "Claude Code automatically keeps itself up to date."

What's Wrong or Missing?

There is a critical discrepancy between the "Advanced Setup" guide and the "Quickstart/Overview" pages. A user following the Quickstart guide who chooses Homebrew or WinGet—likely for convenience—is never informed that they are opting out of the auto-update mechanism mentioned in the Overview.

Because the tool is agentic and has broad system permissions, missing security updates is a high-severity risk. Currently, a user has to dig into the full Setup/Troubleshooting pages to realize their installation is static.

Suggested Improvement

Add a <Note> or <Warning> callout immediately following the installation command tabs in both quickstart.md and overview.md.

Suggested Text:

Note on Updates: Unlike the native installer, Homebrew and WinGet installations do not support background auto-updates. To ensure you have the latest security fixes and features, you must manually run brew upgrade claude-code or winget upgrade Anthropic.ClaudeCode regularly.

Impact

High - Prevents users from using a feature

Additional Context

The main/CHANGELOG.md for version 2.0.33 reinforces this importance, noting that native binary installs are the focus for launch speed and lifecycle management. Relying on the user to check the "Advanced Setup" page for maintenance requirements on a "Quickstart" method creates a "pit of failure" regarding security posture.