claude-code - 💡(How to fix) Fix [BUG] Auto-update failure message appears persistently with no way to suppress it [3 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#56189Fetched 2026-05-06 06:34:49
View on GitHub
Comments
3
Participants
2
Timeline
9
Reactions
0
Timeline (top)
commented ×3labeled ×3renamed ×2cross-referenced ×1

Error Message

There is no way to suppress it. The settings schema has no field to disable auto-update checks — attempting to add "autoUpdates": false to settings.json produces a validation error (Unrecognized field: autoUpdates). The suggested remediation (npm i -g @anthropic-ai/claude-code) is not possible when Claude Code is installed in a read-only location (e.g. a Docker image or managed environment where the install path is intentionally immutable).

Error Messages/Logs

Code Example

Auto-update failed · Try claude doctor or npm i -g @anthropic-ai/claude-code

---

Auto-update failed · Try claude doctor or npm i -g @anthropic-ai/claude-code
RAW_BUFFERClick to expand / collapse

What's Wrong?

After some point in normal use, Claude Code began displaying the following banner on startup:

✗ Auto-update failed · Try claude doctor or npm i -g @anthropic-ai/claude-code

There is no way to suppress it. The settings schema has no field to disable auto-update checks — attempting to add "autoUpdates": false to settings.json produces a validation error (Unrecognized field: autoUpdates). The suggested remediation (npm i -g @anthropic-ai/claude-code) is not possible when Claude Code is installed in a read-only location (e.g. a Docker image or managed environment where the install path is intentionally immutable).

What Should Happen?

Either:

  • A settings field (e.g. "autoUpdates": false) to opt out of the update check entirely, or
  • The updater silently no-ops when the install path is not writable, rather than surfacing a banner with no actionable remediation.

Error Messages/Logs

✗ Auto-update failed · Try claude doctor or npm i -g @anthropic-ai/claude-code

Steps to Reproduce

  1. Install Claude Code globally via npm in a read-only location (e.g. baked into a Docker image).
  2. Start a Claude Code session.
  3. At some point the failure banner begins appearing on startup and cannot be dismissed or suppressed.

Is this a regression?

I don't know — the message was not present initially and appeared after some period of normal use.

Claude Code Version

2.1.126 (Claude Code)

Platform

Anthropic API

Operating System

Linux (container / read-only volume mount)

Terminal/Shell

Non-interactive/CI environment

Additional Information

The core issue is not whether the update check fires on every startup, but that once it starts failing there is no supported way to silence it. In containerised or managed deployments the install path is intentionally immutable, so the failure is permanent and the banner becomes unremediable noise.

extent analysis

TL;DR

The most likely fix is to modify the settings to opt out of auto-update checks or to silently no-op when the install path is not writable.

Guidance

  • Consider modifying the settings.json to include a field that disables auto-update checks, although the current schema does not support this.
  • Investigate if there's an undocumented way to configure the auto-update behavior, as the suggested remediation is not feasible in read-only environments.
  • Look into potential environment variables or command-line flags that could influence the auto-update check.
  • If possible, explore updating the installation to a version that may include a fix for this issue, although the version with the fix is not specified.

Example

No code snippet is provided as the issue does not imply a specific code change.

Notes

The provided information does not include details on how to modify the auto-update behavior directly, and any attempts to add custom fields to the settings result in validation errors.

Recommendation

Apply a workaround by exploring alternative configuration options or environment variables that could disable or silence the auto-update check, as updating the installation may not be feasible in all environments.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING