[BUG] ClaudeCode v1.0.45 hangs when CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC is set

Resolved 💬 20 comments Opened Jul 8, 2025 by damien-king Closed Jul 17, 2025
💡 Likely answer: A maintainer (ashwin-ant, collaborator) responded on this thread — see the highlighted reply below.

Environment

  • Platform (select one):
  • [ ] Anthropic API
  • [x] AWS Bedrock
  • [ ] Google Vertex AI
  • [ ] Other: <!-- specify -->
  • Claude CLI version:1.0.45
  • Operating System: macOS 15.1, Ubuntu 22.0.4
  • Terminal: VSCode terminal, terminal app

Bug Description

When using bedrock, CC immediately hangs on launch and is unresponsive (no keyboard input or ctrl + c etc.) This is not an issue using an Anthropic Max account (I haven't tried Anthropic API key).

Hangs at:

╭───────────────────────────────────────────────────╮
│ ✻ Welcome to Claude Code!                         │
│                                                   │
│   /help for help, /status for your current setup  │
│                                                   │
│   cwd: /Volumes/External/Playground/altec         │
╰───────────────────────────────────────────────────╯


 ※ Tip: Cmd+Escape to launch Claude in your IDE

╭────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ > Try "how does __init__.py work?"                                                                                                                                                                         │
╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
  ? for shortcuts                                                                                                                                                                         ◯ IDE disconnected < 

Steps to Reproduce

  1. Set env (example only, use your own env):
export CLAUDE_CODE_USE_BEDROCK=1
export AWS_REGION=us-east-1 
export AWS_PROFILE=dev
export ANTHROPIC_MODEL='us.anthropic.claude-sonnet-4-20250514-v1:0'
  1. run claude

Expected Behavior

Normal usage

Actual Behavior

terminal input is frozen and cannot use CC.

Additional Context

In VSCode IDE always shows as disconnected but the behaviour in terminal and IDE is identical. I've tried disabling all MCP with no change to behavior.

View original on GitHub ↗

20 Comments

danoc · 1 year ago

I can reliably reproduce this in version 1.0.45 (released ~25 mins ago). The error goes away when downgrading.

hirale · 1 year ago

Confirm.

danoc · 1 year ago

@damien-king — To clarify, I'm not using Bedrock. This issue happens on the $100/mo Claude plan as well.

damien-king · 1 year ago
@damien-king — To clarify, I'm not using Bedrock. This issue happens on the $100/mo Claude plan as well.

Thanks, oddly I'm also using the $100 account on the same install (in a different terminal session) and it works fine for me, it's just when applying the Bedrock env that I see the hang.

hirale · 1 year ago

If you downgrade to 1.0.44, when you reopen it for a while, it will run auto-updating.

danoc · 1 year ago
> @damien-king — To clarify, I'm not using Bedrock. This issue happens on the $100/mo Claude plan as well. Thanks, oddly I'm also using the $100 account on the same install (in a different terminal session) and it works fine for me, it's just when applying the Bedrock env that I see the hang.

Ah, that's odd. I'm about to type a few characters and then it freezes up. I've tried clearing my config files, uninstalling, reinstalling, restarting my computer, and everything I could think of. I also removed the MCP servers but that didn't help.

I also ran claude -d but there were no obvious issues in the logs.

If you downgrade to 1.0.44, when you reopen it for a while, it will run auto-updating.

@hirale — You can run DISABLE_AUTOUPDATER=1 claude in the meantime to prevent auto-update.

damien-king · 1 year ago
Ah, that's odd. I'm about to type a few characters and then it freezes up. I've tried clearing my config files, uninstalling, reinstalling, restarting my computer, and everything I could think of. I also removed the MCP servers but that didn't help. I also ran claude -d but there were no obvious issues in the logs. If you downgrade to 1.0.44, when you reopen it for a while, it will run auto-updating. @hirale — You can run DISABLE_AUTOUPDATER=1 claude in the meantime to prevent auto-update.

I can confirm downgrading to 1.0.44 and setting the DISABLE_AUTOUPDATER workaround the issue for now.

chris-sanders · 1 year ago

I'm not on the 100 plan and am just using the console API account and also get a hang after a few seconds on 1.0.45, also confirmed 1.0.44 works

ashwin-ant collaborator · 1 year ago

If you run with claude --debug can you share the output?

kzwang · 1 year ago

Also run into the same issue as long as CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC=1 is set

timfallmk · 1 year ago

@ashwin-ant There's nothing unusal in the debug logs.

dicksontsai collaborator · 1 year ago

Thanks for the reports everyone. We've paused the rollout of 1.0.45 as the default latest version as we investigate. Please downgrade to 1.0.44 if you are encountering this issue.

Bookman0001 · 1 year ago

It also happens on Google Vertex AI, it might not depend on the platform. Therefore, I downgrade to 1.0.44.

nikolayv · 1 year ago

This was actually happening for me on 1.0.44, and only seems to have stopped after I ran claude update and got 45 10 mins ago.

For me, it was responsive for a few seconds, perhaps up to 5s. Then hung so hard nothing would save the shell short of Cmd + W.

I'm on my 2022 M2 MBA and on Max.

ashwin-ant collaborator · 1 year ago

We've identified the root cause and it was a regression in 1.0.45. We have a fix in place in 1.0.46, but for now we've marked 1.0.44 as the latest version so no one should get auto-updated.

holstvoogd · 1 year ago

FYI: Running claude update downgrades to 1.0.44 now and that seems to work again for me.

kateliu20 · 1 year ago

Having the same issue with 1.0.45, but bumping the version back down to 1.0.44 works normally.

markdrake · 12 months ago

Had the same issue today. Not sure why it upgraded to v1.0.45 but it's currently broken. Downgrading to v1.0.44 works as many other have reported.

ashwin-ant collaborator · 12 months ago

@markdrake you should be able to upgrade past 1.0.45 now. 1.0.55 is the latest version.

github-actions[bot] · 11 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.