Skip to content

[Bug]: Claude code doesn't support AWS Bedrock usage #1257

Closed

Description

@super-original

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.

Area

apps/web

Steps to reproduce

  1. Have your claude code set up to use AWS Bedrock
  2. Double check that claude code works in the CLI
  3. Attempt to prompt in T3 Chat with a claude model
  4. You will get "Credit balance is too low" response

Expected behavior

The model responds normally.

Actual behavior

The only response is "Credit balance is too low"

Impact

Blocks work completely

Version or commit

0.0.13

Environment

MacOS 26.3.1, T3 Code 0.0.13, Any anthropic model

Logs or stack traces

Screenshots, recordings, or supporting files

CleanShot 2026-03-21 at 00.30.05.png
CleanShot 2026-03-21 at 00.29.53.png

Workaround

Use Claude code in the CLI until this is fixed

Activity

  1. added
    bugSomething is broken or behaving incorrectly.
    needs-triageIssue needs maintainer review and initial categorization.
    on Mar 20, 2026
  2. Noojuno commented on Mar 21, 2026

    @Noojuno
    Contributor

    @super-original I will have a look at this now!

    How are you setting up Claude Code to use bedrock?

  3. super-original commented on Mar 21, 2026

    @super-original
    Author

    @Noojuno
    I have the following environment variables set in ~/.claude/settings.json under the "env" key:

    {
      "env": {
        "CLAUDE_CODE_USE_BEDROCK": "1",
        "AWS_REGION": "us-east-1",
        "AWS_DEFAULT_REGION": "us-east-1",
        "ANTHROPIC_DEFAULT_OPUS_MODEL": "us.anthropic.claude-opus-4-6-v1"
      }
    }
    

    For AWS auth, I'm using IAM credentials from the root account configured in ~/.aws/config with the default profile (not SSO). Claude Code in the CLI works perfectly with this setup, it's only T3 Code that returns "Credit balance is too low", which makes me think T3 Code might be checking for an Anthropic API key/credits instead of passing through the Bedrock configuration.

  4. rkarimpour-diligent commented on Mar 23, 2026

    @rkarimpour-diligent

    Same issue here. I found that you can force T3 to pick those settings up by explicitly adding them to the environment variables and then run T3 from terminal using the full binary path /Applications/T3 Code (Alpha).app/Contents/MacOS/T3 Code (Alpha).

  5. harshit97 commented on Mar 23, 2026

    @harshit97
    Contributor

    @rkarimpour-diligent @super-original @Noojuno hey folks, can you look at the change in my PR? If you've got the time, run it locally and see if it fixes things for you. It makes Claude work for me across the board with different types of auth modes, but it would be awesome to get more data points from you guys.

  6. wagnersza commented on Mar 24, 2026

    @wagnersza

    Same bug here

  7. dafzthomas commented on Mar 25, 2026

    @dafzthomas

    In my case, my work uses AWS SSO to authenticate the with the bedrock ARN's. If these are within the harness then should trigger as it would inside Claude Code?

  8. dafzthomas commented on Mar 27, 2026

    @dafzthomas

    So if the Bedrock settings are set inside ~/.claude/settings.json, and you add custom Claude models pointing to your model arns in the settings - it works.

  9. tijmenvangurp commented on Jun 8, 2026

    @tijmenvangurp

    Worked for me (AWS SSO setup):

    Two things needed:

    1. Add Bedrock env vars to ~/.claude/settings.json:

    "env": {
      "CLAUDE_CODE_USE_BEDROCK": "1",
      "AWS_REGION": "us-east-1",
      "AWS_DEFAULT_REGION": "us-east-1",
      "AWS_PROFILE": "your-sso-profile-name"
    }

    AWS_PROFILE is required if you use SSO with named profiles and no default profile — without it T3 can't resolve credentials.

    2. Set the model in T3's instance Launch arguments:

    --model us.anthropic.claude-sonnet-4-5-20250929-v1:0
    

    T3 defaults to the us.anthropic.claude-sonnet-4-6 format which is invalid for Bedrock. Adding --model with the correct versioned Bedrock ID in the instance config fixes the "model identifier is invalid" error.

  10. sudo-tmoney29 commented on Nov 4, 2026

    @sudo-tmoney29

    @tijmenvangurp - Can you only use this for Anthropic models? In Bedrock, I have access to 155 endpoints. I am desiring to bring in 5-6-7, different models as council members to hill climb ideas.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething is broken or behaving incorrectly.needs-triageIssue needs maintainer review and initial categorization.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions