Feature request: AWS Bedrock authentication through environment variables

[josf]

It would be great to be able to use models through AWS Bedrock, using the AWS credentials in environment variables. (In fact, this is the only way we're allowed to use LLMs at work.)

To use claude-code.el, for example, I add these to my use-package:

         :config 
        (setenv "CLAUDE_CODE_USE_BEDROCK" "1")
        (setenv "AWS_REGION" "eu-west-1")
        (setenv "AWS_PROFILE" "my-aws-profile")
        (setenv "ANTHROPIC_MODEL" "eu.anthropic.claude-opus-4-6-v1")

Having something similar in agent-shell would allow me to use agent-shell instead.

If there's interest in this feature, I have it working on a PR on my fork.

Checklist

• I agree to communicate with the author myself (not AI-generated).
• I've read the README's Filing issues section.
• I'm running the latest versions (fill in below).
  • agent-shell version: v0.50.1
  • acp.el version: v0.11.3
  • ACP package (e.g. claude-agent-acp) version: 0.23.1
  • Agent CLI (e.g. claude, gemini) version: claude v2.1.89
• For requesting new agent support, I'm including a link to the ACP-capable agent or related ACP package.
• For issues, I'm including ACP traffic (as per README).

[skeezix]

For work, we have Bedrock, but not a profile, though I think I can get the user-id (which is profile?) from sts get on aws-cli

To get into Claude cli today, we use AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY and region, and use_bedrock, and good to go on cli

With your PR here, it just seems to hang for a couple minutes and error out (claims auth in the acp traffic log buffer.)

Curiously, if I run the claude-acp-agent daemon by hand and enter the json-rpc commands into it to create a session and query the session, it works fine; so I know the stack is okay, and its probably just something I'm missing in the patch above..

But I can second the merge perhaps, as it looks passive to the base code, and gets some folks closet, and I can bash on it if I get time.

[josf]

For work, we have Bedrock, but not a profile, though I think I can get the user-id (which is profile?) from sts get on aws-cli

To get into Claude cli today, we use AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY and region, and use_bedrock, and good to go on cli

With your PR here, it just seems to hang for a couple minutes and error out (claims auth in the acp traffic log buffer.)

I think some of this depends on how things are set up on the AWS account as well. I struggled quite a bit the first time, to get claude-code.el to work with Bedrock.

Curiously, if I run the claude-acp-agent daemon by hand and enter the json-rpc commands into it to create a session and query the session, it works fine; so I know the stack is okay, and its probably just something I'm missing in the patch above..

But I can second the merge perhaps, as it looks passive to the base code, and gets some folks closet, and I can bash on it if I get time.

I actually want to check another way of doing this. It might be possible to achieve the same thing my patch does by using the environment variable support in agent-shell. As soon as I get some time, I'll double check that.

[skeezix]

ah cool; if you can let me know here as well. Bedrock is cute, but I iamgine people use litellm (recently hacked) or openrouter or the like for this kind of thing, as bedrock support to models is so generally flaky across tools :/