claude-code - 💡(How to fix) Fix [BUG] showSetupScreens() bedrock-fallback tier probing adds ~4.3s to startup [3 comments, 3 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#49138Fetched 2026-04-17 08:49:49
View on GitHub
Comments
3
Participants
3
Timeline
8
Reactions
0
Author
Timeline (top)
labeled ×5commented ×3

Error Message

Error Messages/Logs

Fix Action

Fix / Workaround

Since recent Claude Code patches, startup takes ~5 seconds before the REPL becomes interactive.

Code Example

> 2026-04-16T11:43:06.807Z [DEBUG] Fetching AWS caller identity for AWS auth refresh command
> 2026-04-16T11:43:07.299Z [DEBUG] Fetched AWS caller identity, skipping AWS auth refresh command
> 2026-04-16T11:43:11.586Z [DEBUG] [bedrock-fallback] unpinnedTiers=3 fallbacks=0
> 2026-04-16T11:43:11.587Z [DEBUG] [STARTUP] showSetupScreens() completed in 4723ms
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?

Since recent Claude Code patches, startup takes ~5 seconds before the REPL becomes interactive.

Debug logs (--debug) show showSetupScreens() takes 4723ms, with ~4300ms spent between the AWS caller identity resolution and the [bedrock-fallback] unpinnedTiers=3 fallbacks=0 log line. The bedrock-fallback tier probing appears to make blocking network requests that gate the entire startup path.

What Should Happen?

Startup should be near-instant (sub-1s). Furthermore, according to Claude Code itself, "the bedrock-fallback tier probing should either run in the background (non-blocking), be cached across sessions, or use shorter timeouts".

Prior versions did not have this delay.

Error Messages/Logs

> 2026-04-16T11:43:06.807Z [DEBUG] Fetching AWS caller identity for AWS auth refresh command
> 2026-04-16T11:43:07.299Z [DEBUG] Fetched AWS caller identity, skipping AWS auth refresh command
> 2026-04-16T11:43:11.586Z [DEBUG] [bedrock-fallback] unpinnedTiers=3 fallbacks=0
> 2026-04-16T11:43:11.587Z [DEBUG] [STARTUP] showSetupScreens() completed in 4723ms

Steps to Reproduce

  1. Configure Claude Code to use an AWS Bedrock-routed model (e.g. eu.anthropic.claude-opus-4-6-v1[1m])
  2. Launch Claude Code with --debug
  3. Observe ~5s delay before the REPL becomes interactive
  4. In the debug log, search for showSetupScreens() — it reports ~4700ms
  5. The gap between Fetched AWS caller identity and [bedrock-fallback] unpinnedTiers=3 is ~4.3s

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

~2 weeks ago

Claude Code Version

2.1.110 (Claude Code)

Platform

AWS Bedrock

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Other

Additional Information

  • Terminal Ghostty v1.2.3

  • Model: eu.anthropic.claude-opus-4-6-v1[1m] (EU Bedrock region)

  • The showSetupScreens() function accounts for 95% of total startup time (4723ms of ~4940ms)

  • Breakdown: AWS caller identity takes ~493ms (acceptable), then bedrock-fallback probing takes ~4287ms across 3 unpinned tiers with 0 fallbacks used — suggesting the probing is wasted work in this case

  • Everything after showSetupScreens() is fast: MCP connections, LSP init, file indexing all complete in background after REPL mount

  • Node v24.3.0, Linux 6.17.0-22-generic (Ubuntu 25.x)

extent analysis

TL;DR

The most likely fix is to modify the bedrock-fallback tier probing to run in the background or use shorter timeouts to reduce the blocking network requests that cause the startup delay.

Guidance

  • Investigate the showSetupScreens() function to identify the specific code responsible for the bedrock-fallback tier probing and modify it to run in the background or use shorter timeouts.
  • Verify that the AWS caller identity resolution is not the cause of the delay, as the logs indicate it takes only ~493ms.
  • Consider caching the results of the bedrock-fallback tier probing across sessions to avoid repeated blocking requests.
  • Review the Claude Code documentation and AWS Bedrock configuration to ensure that the setup is correct and optimized for performance.

Example

No code snippet is provided as the issue does not include specific code details, but the showSetupScreens() function and bedrock-fallback tier probing logic should be reviewed and modified to address the startup delay.

Notes

The issue is specific to the Claude Code version 2.1.110 and the Opus model on AWS Bedrock, and the delay is caused by the bedrock-fallback tier probing. The fix may require modifications to the Claude Code or AWS Bedrock configuration.

Recommendation

Apply a workaround by modifying the bedrock-fallback tier probing to run in the background or use shorter timeouts, as the current implementation is causing a significant startup delay. This change should improve the performance of the Claude Code startup process.

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

claude-code - 💡(How to fix) Fix [BUG] showSetupScreens() bedrock-fallback tier probing adds ~4.3s to startup [3 comments, 3 participants]