claude-code - 💡(How to fix) Fix Auto-updater silently downgrades binary when current version exceeds stable channel head (2.1.143 → 2.1.133 revert on Windows)

Summary

On Windows, after a one-time force-install of CC 2.1.143 with autoUpdatesChannel: "stable" left unchanged, the bridge binary at ~/.local/bin/claude.exe silently reverted 2.1.143 → 2.1.133 within ~80 minutes. The stable channel head was 2.1.133 at the time. Setting autoUpdatesChannel: "latest" + minimumVersion: "2.1.143" stopped the revert; a 13-tick / 60-minute watcher confirmed stickiness after the change.

The observed behavior is consistent with the auto-updater enforcing current_binary == channel_head on a timer (force-downgrade when current > head), not the expected upgrade-only-forward (current >= head).

Environment

• OS: Windows 11 Pro 26300, pwsh 7.6.1
• Binary path: C:\Users\<u>\.local\bin\claude.exe
• Install vector: iex (irm https://claude.ai/install.ps1) 2.1.143
• Channel before fix: stable (head = 2.1.133)
• Channel after fix: latest + minimumVersion: "2.1.143"

Timeline (2026-05-17 EDT)

Expected

A binary at a version higher than the active channel head should not be downgraded silently.

Actual

Binary was downgraded to channel head despite being newer.

Workaround

// ~/.claude/settings.json and ~/.claude/settings.local.json
{
  "autoUpdatesChannel": "latest",
  "minimumVersion": "2.1.143"
}

Asks

1. Confirm whether the updater intentionally enforces current == channel_head on stable.
2. If unintentional: patch to forward-only semantics on stable.
3. If intentional: document explicitly that stable will downgrade a higher-version binary to head, so users running off-channel forces understand the contract.

Related

Prior issue #59450 (Round-17 stability diagnostic, 2.1.142 upgrade, dispatch-path version-split).