Preflight Checklist
What's Wrong?
Three clarifications needed:
-
Setting precedence — When multiple disable-auto-update paths exist (disableAutoUpdates in settings.json, CLAUDE_DISABLE_AUTO_UPDATES env var, claude --disable-auto-updates flag), which takes precedence? Is there a documented order?
-
Notification behavior with auto-updates disabled — When auto-updates are disabled via settings, does claude doctor or startup still notify that a newer version is available (without auto-installing)? Goal: keep updates visible as pending without automatic installation.
-
Canonical CHANGELOG URL — Where is the official release notes/CHANGELOG for pre-install review? (Not third-party blogs, the canonical Anthropic URL.)
Use case: update gate workflow where a reviewer manually runs claude update only after evaluating the changelog.
What Should Happen?
To resolve the issue, maintainers should:
- Document setting precedence — Clarify which wins (if you set all three: flag + env var + settings.json, which is honored?). If undefined, implement and document the precedence.
- Document notification behavior — Confirm/guarantee that claude doctor (or startup banner) shows "version X available" when auto-updates are disabled, so pending updates remain visible without auto-installing.
- Provide canonical CHANGELOG URL — Link the official release notes location in setup docs (likely https://code.claude.com/docs/en/changelog.md or a releases page).
Why it matters: use case is update-gate workflow — disable auto-update → reviewer checks CHANGELOG → manually run claude update. Docs need to guarantee #1 (updates won't install accidentally) and #2 (updates won't be hidden).
When you file the issue, the maintainers will either:
- Answer the questions (clarifying what already works)
- File related bugs if behavior is broken
- Update docs if it's just missing clarity
Error Messages/Logs
✘ Auto-update failed · Run claude doctor
Steps to Reproduce
Environment: Native Claude Code install on Linux
-
Set disableAutoUpdates in ~/.claude/settings.json:
{
"disableAutoUpdates": true
}
-
Verify auto-update is actually disabled:
- Wait 24h OR manually trigger a check (method TBD — not documented)
- Confirm no auto-install happens
-
Check if version-available notification still appears:
- Run: claude doctor
- Run: claude (start a session)
- Expected: notification that version X.Y.Z is available (without installing)
- Actual: [unclear — needs clarification]
-
Test setting precedence (if multiple disable paths exist):
- Set in settings.json: disableAutoUpdates=true
- Set in env: export CLAUDE_DISABLE_AUTO_UPDATES=1
- Run: claude update
- Result: [which setting wins? — not documented]
-
Pre-install review workflow:
- Check official CHANGELOG before running: claude update
- Current URL: [unknown — needs canonical source]
Claude Model
Other
Is this a regression?
Yes, this worked in a previous version
Last Working Version
No response
Claude Code Version
Current version 2.1.218
Platform
Anthropic API
Operating System
Other Linux
Terminal/Shell
Non-interactive/CI environment
Additional Information
Linux CLI Fedora 44 WS
Preflight Checklist
What's Wrong?
Three clarifications needed:
Setting precedence — When multiple disable-auto-update paths exist (
disableAutoUpdatesin settings.json,CLAUDE_DISABLE_AUTO_UPDATESenv var,claude --disable-auto-updatesflag), which takes precedence? Is there a documented order?Notification behavior with auto-updates disabled — When auto-updates are disabled via settings, does
claude doctoror startup still notify that a newer version is available (without auto-installing)? Goal: keep updates visible as pending without automatic installation.Canonical CHANGELOG URL — Where is the official release notes/CHANGELOG for pre-install review? (Not third-party blogs, the canonical Anthropic URL.)
Use case: update gate workflow where a reviewer manually runs
claude updateonly after evaluating the changelog.What Should Happen?
To resolve the issue, maintainers should:
Why it matters: use case is update-gate workflow — disable auto-update → reviewer checks CHANGELOG → manually run claude update. Docs need to guarantee #1 (updates won't install accidentally) and #2 (updates won't be hidden).
When you file the issue, the maintainers will either:
Error Messages/Logs
Steps to Reproduce
Environment: Native Claude Code install on Linux
Set disableAutoUpdates in ~/.claude/settings.json:
{
"disableAutoUpdates": true
}
Verify auto-update is actually disabled:
Check if version-available notification still appears:
Test setting precedence (if multiple disable paths exist):
Pre-install review workflow:
Claude Model
Other
Is this a regression?
Yes, this worked in a previous version
Last Working Version
No response
Claude Code Version
Current version 2.1.218
Platform
Anthropic API
Operating System
Other Linux
Terminal/Shell
Non-interactive/CI environment
Additional Information
Linux CLI Fedora 44 WS