claude-code - 💡(How to fix) Fix [BUG] Download failed. Check your connection when starting new session — 404 on model config [1 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#45092Fetched 2026-04-09 08:13:28
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Timeline (top)
labeled ×2commented ×1unlabeled ×1

Error Message

Error shown: "Download failed. Check your connection and try again." Error 1 — model config 404: Error 2 — repeated fetch failures: 3. Error appears immediately

Error Messages/Logs

Actual: Error "Download failed. Check your connection and try again." This returns 404 (likely because brackets are not URL-encoded, or because this model variant is not available for my org). The error blocks new session creation entirely, even though existing sessions still work. [REACT_QUERY_CLIENT] QueryClient error: {"type":"not_found_error","statusCode":404,

Root Cause

This returns 404 (likely because brackets are not URL-encoded, or because this model variant is not available for my org). The error blocks new session creation entirely, even though existing sessions still work.

Fix Action

Fix / Workaround

Attempted workarounds that did NOT help:

  • Restart the app (Cmd+Q + reopen)
  • Restart the Mac
  • Clear ~/.claude/cache
RAW_BUFFERClick to expand / collapse

Preflight Checklist

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

What's Wrong?

Problem

Cannot start new sessions in Claude Code desktop app (macOS). Error shown: "Download failed. Check your connection and try again." Existing sessions continue to work normally.

Logs (~/Library/Logs/Claude/claude.ai-web.log)

Error 1 — model config 404: endpoint: /api/organizations/.../model_configs/claude-opus-4-6[1m] statusCode: 404 message: "Not found"

Error 2 — repeated fetch failures: TypeError: Failed to fetch (assets-proxy.anthropic.com)

Steps to reproduce

  1. Open Claude Code desktop app
  2. Click "New session"
  3. Error appears immediately

Environment

  • macOS Darwin 25.2.0
  • Tried: restart app, restart Mac, cleared cache — no effect
  • Network: api.anthropic.com responds (curl returns HTTP/2 404 as expected)

What Should Happen?

Starting a new session should work normally — the app should connect to the Anthropic API, load the selected model config, and open an empty chat ready for input.

Instead, clicking "New session" shows "Download failed. Check your connection and try again." immediately. Existing sessions continue to work fine, which suggests the issue is specifically in the new-session initialization flow (model config fetch + asset proxy).

Logs show two related errors:

  1. 404 Not Found on /api/organizations/{org_id}/model_configs/claude-opus-4-6[1m]
  2. TypeError: Failed to fetch against assets-proxy.anthropic.com

App version: 1.1062.0 (macOS Darwin 25.2.0) Restarting app, restarting Mac, and clearing cache did not help. Direct curl to api.anthropic.com works fine.

Error Messages/Logs

Steps to Reproduce

  1. Open Claude Desktop app (version 1.1062.0 on macOS)
  2. Inside an existing session, run: /model claude-opus-4-6[1m]
  3. Close the app completely (Cmd+Q)
  4. Reopen the app
  5. Click "New session" (or try to start any new conversation)

Expected: New session opens normally Actual: Error "Download failed. Check your connection and try again."

The app appears to persist the selected model name including the [1m] suffix, then tries to fetch its config from: /api/organizations/{org_id}/model_configs/claude-opus-4-6[1m]

This returns 404 (likely because brackets are not URL-encoded, or because this model variant is not available for my org). The error blocks new session creation entirely, even though existing sessions still work.

Attempted workarounds that did NOT help:

  • Restart the app (Cmd+Q + reopen)
  • Restart the Mac
  • Clear ~/.claude/cache

Environment:

  • App version: 1.1062.0
  • OS: macOS Darwin 25.2.0
  • Network: api.anthropic.com reachable (curl -I returns HTTP/2 as expected)

Log excerpt from ~/Library/Logs/Claude/claude.ai-web.log: [REACT_QUERY_CLIENT] QueryClient error: {"type":"not_found_error","statusCode":404, "endpoint":"/api/organizations/.../model_configs/claude-opus-4-6[1m]", "method":"GET","message":"Not found"}

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

Claude Desktop версия: 1.1062.0

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

The issue is likely due to the app attempting to fetch a model config with a malformed URL, causing a 404 error, and can be worked around by ensuring the model name is properly URL-encoded or by selecting a different model.

Guidance

  • Verify that the model name claude-opus-4-6[1m is correctly formatted and URL-encoded when making the API request to /api/organizations/{org_id}/model_configs/.
  • Check if the issue persists when trying to start a new session with a different model, to isolate if the problem is specific to the claude-opus-4-6[1m model.
  • Consider clearing any cached model configurations or preferences that may be causing the app to persist the malformed model name.
  • Test if manually removing the [1m suffix from the model name resolves the issue, as this may indicate a character encoding or formatting problem.

Example

No code example is provided as the issue seems related to the app's configuration or API request formatting rather than a code snippet that can be directly modified.

Notes

The exact cause of the malformed model name and how it's being persisted across app restarts is unclear. Further investigation into the app's configuration and caching mechanisms may be necessary to fully resolve the issue.

Recommendation

Apply a workaround by trying a different model or manually correcting the model name to ensure it's properly formatted, as the root cause of the malformed URL is not immediately clear and may require further investigation or support from the app developers.

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