[DOCS] Npm update docs do not explain release-channel behavior for `claude update`

Documentation Type

Unclear/confusing documentation

Documentation Location

https://code.claude.com/docs/en/setup

Section/Topic

Update Claude Code, Configure release channel, and Install with npm

Current Documentation

The setup page currently says:

Control which release channel Claude Code follows for auto-updates and claude update with the autoUpdatesChannel setting:

The same page later says:

To apply an update immediately without waiting for the next background check, run:

claude update

But the npm-specific installation section says:

To upgrade an npm installation, run npm install -g @anthropic-ai/claude-code@latest. Avoid npm update -g, which respects the semver range from the original install and may not move you to the newest release.

What's Wrong or Missing?

The docs do not explain how claude update behaves for npm installations when the user has configured the stable release channel.

The v2.1.153 changelog says Claude Code fixed claude update installing the latest version instead of the configured release channel's version for npm installations. That implies npm-installed Claude Code should be able to honor autoUpdatesChannel, but the npm section only documents an explicit @latest npm command.

As written, npm users who want the stable channel cannot tell whether they should:

1. use claude update and rely on autoUpdatesChannel,
2. use a different npm dist tag or version pin,
3. avoid npm for stable-channel updates, or
4. ignore autoUpdatesChannel because npm updates are always latest-only.

Suggested Improvement

Update the npm installation section to clarify the supported update paths for npm installs.

Suggested minimum fix:

For npm installations, claude update honors your configured autoUpdatesChannel (latest or stable). Use claude update when you want Claude Code to follow that configured channel. Use npm install -g @anthropic-ai/claude-code@latest only when you explicitly want the npm latest release.

If npm installations have limitations that differ from native installer updates, document those limitations in the same section and cross-reference Configure release channel.

Also update the claude update row in the CLI reference so it does not imply latest-only behavior.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/setup | 205-220 | autoUpdatesChannel says it controls claude update, but only calls out Homebrew channel behavior by cask name |
| https://code.claude.com/docs/en/setup | 253-258 | Manual update section tells users to run claude update without clarifying npm release-channel behavior |
| https://code.claude.com/docs/en/setup | 396-408 | npm section tells users to run npm install -g @anthropic-ai/claude-code@latest, with no stable-channel or claude update guidance |
| https://code.claude.com/docs/en/cli-reference | 22 | claude update is described as "Update to latest version" even though v2.1.153 says npm claude update now honors the configured release channel |

Total scope: 2 pages affected

Version context: v2.1.153 changelog entry:

Fixed claude update installing the latest version instead of the configured release channel's version for npm installations