ant-kurt
ant-kurt
Thanks for the report - we have repro on this and are working through this along with the other login-related issues (see #1582). @dvarnai if you have a preference on...
@deanbear can you provide more details on your configuration: - How are you passing the LiteLLM URL (which env var)? - Which LiteLLM endpoints are you using - passthrough or...
Does your LiteLLM live on localhost? In working to repro this, I noticed some weirdness when using both a local proxy and a local LiteLLM. Are you expecting HTTP CONNECT...
Hi @indrasvat - I'm not able to reproduce this on my end. If you run with `DEBUG=true`, you can see the requests going out. Can you confirm that the payloads...
Thanks for the thorough investigation on this @indrasvat - I'm circling back with the team and will provide an update.
@indrasvat - unfortunately we don't have a workaround for this right now, other than passing in fewer tools. Appreciate your investigation on this!
`ANTHROPIC_LOG=debug` is the replacement for `DEBUG=true`. If your tool count is 17, I wouldn't expect the default tools in Claude Code to be pushing you over 128 total tools. Once...
@msmygit how are you authenticating to Bedrock? This 403 indicates your credentials are expired, and you'll need to run something like `aws configure`, `aws sso login`, or set new `AWS_*`...
Hmm - are you passing `AWS_PROFILE=bedrock` to Claude Code as well?
Hmm - I don't think we've made any changes to the AWS auth flow here, in that we require either an `AWS_PROFILE` with relevant `.aws` entries, or `AWS_ACCESS_KEY_ID` + `AWS_SECRET_ACCESS_KEY`...