claude-code - 💡(How to fix) Fix [BUG] i've started using amazon Badrock API and now i'm not able to use claude subscription. [2 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#55950Fetched 2026-05-05 06:02:06
View on GitHub
Comments
2
Participants
2
Timeline
7
Reactions
0
Timeline (top)
labeled ×4commented ×2closed ×1

Error Message

Error Messages/Logs

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?

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

extent analysis

TL;DR

Remove existing credentials and restart Claude Code to ensure the new subscription login is used instead of falling back to the billing API.

Guidance

  • Verify that the settings.json file is correctly updated after removing credentials to prevent any cached or leftover data from interfering with the new login attempt.
  • Try clearing any temporary or cache files associated with Claude Code to ensure a clean start after removing credentials.
  • Confirm that the Amazon API and Bedrock API key (bearer token) are correctly configured and valid for the subscription login.
  • After relogin with the subscription, check the Claude Code settings or logs to see if it acknowledges the subscription and does not default to the billing API.

Notes

The issue might be related to how Claude Code handles credential storage or caching, which could lead to the fallback behavior even after removing credentials from the settings.json file.

Recommendation

Apply workaround: Remove credentials, clear cache, and restart Claude Code to ensure the new subscription login is recognized, as the root cause of the fallback behavior is not explicitly stated and may require further investigation.

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] i've started using amazon Badrock API and now i'm not able to use claude subscription. [2 comments, 2 participants]