[BUG] Pointless timeout prevents updates over slow internet connections

Status Open
Reported on v2.1.237
Maintainer reply None cached
Activity 1 comment · opened Aug 24, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

When trying to update Claude Code on a slow[^1] but otherwise functioning internet connection, the update will time out due to a pointless 10-minute timeout applied to the time it takes to download the binary.

What Should Happen?

There shouldn't be a timeout on the download itself. So long as bytes are flowing, that means it will eventually manage to download the thing and there is no reason to abort the download just because it's slow. The only timeout should be for cases when there's no progress _at all_, which would suggest something is wrong.

Error Messages/Logs

$ claude update
Current version: 2.1.237
Checking for updates to latest version...
Updating to 2.1.241...
Error: Failed to install native update
TelemetrySafeError: Download timed out: exceeded the total deadline
Try running "claude doctor" for diagnostics

Steps to Reproduce

  1. Be on a slightly outdated Claude Code version.
  2. Have a sufficiently slow[^1] internet connection, i.e. much less than is required to download the new binary within 10 minutes.
  3. Run claude update, thus starting the download.
  4. Wait 10 minutes for the download to time out.

Claude Model

Not sure / Multiple models

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.237

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Other

Additional Information

NOTE: I checked "I am using the latest version of Claude Code" despite being on a slightly older one (2.1.237), because I obviously can't test its update functionality if I'm on the latest version already! Given the lack of other issues about this, I'm just going to assume this hasn't been fixed in more recent versions either.

Workarounds
  • Claude found out that setting the CLAUDE_CODE_DOWNLOAD_DEADLINE_MS_FOR_TESTING env var to a sufficiently large value (e.g. 3600000 = one hour, enough time to download the 2.1.241 340 MB binary over a ~0.75 Mbit/s connection) lets the update proceed.
  • As the name implies, this is clearly a testing/debug feature and not meant for end users, can be removed at any time etc. Hence no replacement for actually removing the timeout.
Related issues and why this isn't a duplicate of them

Footnotes

[^1]: The exact threshold depends on the current binary size: at version 2.1.241, the binary download was ~340 MB, so with the 10 minute timeout the minimum required bandwidth was ~558 KB/s ≈ 4.5 Mbit/s. The binary size has been reduced to ~75 MB in 2.1.243, so it's now lower. But the basic issue itself still exists.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗