You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Claude code doesn't support AWS Bedrock usage #1257
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.
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).
@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.
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?
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.
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.
@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.
Activity
Noojuno commentedon Mar 21, 2026
@super-original I will have a look at this now!
How are you setting up Claude Code to use bedrock?
super-original commentedon Mar 21, 2026
@Noojuno
I have the following environment variables set in
~/.claude/settings.jsonunder the"env"key:For AWS auth, I'm using IAM credentials from the root account configured in
~/.aws/configwith 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.rkarimpour-diligent commentedon Mar 23, 2026
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).harshit97 commentedon Mar 23, 2026
@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.
wagnersza commentedon Mar 24, 2026
Same bug here
dafzthomas commentedon Mar 25, 2026
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?
dafzthomas commentedon Mar 27, 2026
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.tijmenvangurp commentedon Jun 8, 2026
Worked for me (AWS SSO setup):
Two things needed:
1. Add Bedrock env vars to
~/.claude/settings.json:AWS_PROFILEis required if you use SSO with named profiles and nodefaultprofile — without it T3 can't resolve credentials.2. Set the model in T3's instance Launch arguments:
T3 defaults to the
us.anthropic.claude-sonnet-4-6format which is invalid for Bedrock. Adding--modelwith the correct versioned Bedrock ID in the instance config fixes the "model identifier is invalid" error.sudo-tmoney29 commentedon Nov 4, 2026
@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.