claude-code - 💡(How to fix) Fix [BUG] Misleading 'API Usage Billing' label when using Bedrock via settings.json env block [1 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#54707Fetched 2026-04-30 06:38:15
View on GitHub
Comments
0
Participants
1
Timeline
5
Reactions
0
Participants
Timeline (top)
labeled ×5

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?

Status bar shows 'API Usage Billing' instead of 'Bedrock' when Bedrock is configured via env block in settings.json without a saved login — claude auth status correctly shows apiProvider: bedrock in Claude Code v2.1.123.

What Should Happen?

Claude Code should show the correct auth status.

Error Messages/Logs

Steps to Reproduce

Start Claude Code in terminal and see what is shown. Verify by logging out and re-login. Execute claude auth status to see that the API provider is in fact Bedrock.

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

The last version I used before updating - unfortunately I don't know the exact version.

Claude Code Version

2.1.123 (Claude Code)

Platform

AWS Bedrock

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

The issue can likely be resolved by saving a login in the settings.json file or investigating the authentication flow in Claude Code version 2.1.123.

Guidance

  • Verify that the apiProvider is correctly set to bedrock in the settings.json file and that a login is saved.
  • Check the authentication status using claude auth status to confirm that the API provider is recognized as Bedrock.
  • Investigate the differences in authentication behavior between the current version (2.1.123) and the last known working version to identify potential regressions.
  • Test the status bar display after saving a login in the settings.json file to see if it resolves the issue.

Notes

The exact last working version is unknown, which may limit the ability to identify the specific regression. Additionally, the empty error messages/logs section suggests that there may not be any explicit error messages to guide the debugging process.

Recommendation

Apply workaround: Save a login in the settings.json file and verify that the status bar displays the correct auth status, as this is a non-invasive step that can help identify if the issue is related to the authentication flow.

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] Misleading 'API Usage Billing' label when using Bedrock via settings.json env block [1 participants]