Startup time regression in v2.1.9 (~5 min vs normal in v2.1.7)

Resolved 💬 3 comments Opened Jan 16, 2026 by vdirienzo Closed Jan 19, 2026

Bug: Startup time regression in v2.1.9

Environment

  • OS: Linux (Debian-based)
  • Claude Code version with issue: 2.1.9
  • Claude Code version working: 2.1.7
  • Installation method: VSCode Extension
  • Backend: AWS Bedrock (us-east-1)
  • MCP Servers: 3 (sequential-thinking, context7, semgrep)
  • Plugins: frontend-design, feature-dev

Description

Starting Claude Code v2.1.9 takes approximately 5 minutes to fully initialize.
The same configuration on v2.1.7 starts in the expected time (a few seconds).

No changes were made to the configuration between versions - only the Claude Code version differs.

Steps to Reproduce

  1. Install Claude Code 2.1.9 via VSCode Extension
  2. Configure with AWS Bedrock backend (CLAUDE_CODE_USE_BEDROCK=1)
  3. Run claude command (or open Claude Code panel in VSCode)
  4. Observe ~5 minute startup delay before the CLI becomes responsive

Expected Behavior

Startup should take a few seconds, as it does in v2.1.7

Actual Behavior

Startup takes approximately 5 minutes with no visible indication of what is happening during this time.

Workaround

Downgrade to v2.1.7 (via VSCode Extension version management or manual installation)

Additional Context

  • Tested with the same ~/.claude/settings.json configuration
  • MCP servers are the same ones that work fine in 2.1.7
  • No errors displayed during the slow startup
  • Once started, the CLI works normally
  • Installation is via VSCode Extension, not npm

---
Reported via Claude Code

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗