[BUG] i've started using amazon Badrock API and now i'm not able to use claude subscription.

Status Fixed / completed
Maintainer reply None cached
Activity 3 comments · opened May 4, 2026 · closed May 4, 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?

recent days i'm using amazon badrock API and when i try login with the claude subscription, it should successfully logged in, but still i'm not able to use it. it's falling back to the billing API. i've removed credentialss from the settingss.json file as well. but still when i relaunch claude code it shows API biling Use and using the Ammazon API insted of the claude subscription

What Should Happen?

it should have to work with the subsccription when i login with the subscription again,

Error Messages/Logs

Steps to Reproduce

simply login with the amazon API along with the Bedrock API key (bearer token). and than try to relogin with the subscription.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

v2.1.126

Platform

AWS Bedrock

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

_No response_

View original on GitHub ↗

3 Comments

github-actions[bot] · 5 months ago

Found 1 possible duplicate issue:

  1. https://github.com/anthropics/claude-code/issues/55532

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

sagarnabhoya · 5 months ago

i've remove the "CLAUDE_CODE_USE_BEDROCK": "1" from the settings.json file and now it's working, but i guess it should be work automatically while switching.

github-actions[bot] · 3 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.