[FEATURE] AWS Bedrock authentication support for Chrome extension

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Our organization uses AWS Bedrock for Claude access. The CLI supports this via CLAUDE_CODE_USE_BEDROCK=1, but the Chrome extension only supports Claude.ai account login. Users with Bedrock-only access cannot use the extension at all, creating an inconsistency where CLI works but extension doesn't.

Proposed Solution

Add Bedrock authentication to the Chrome extension, matching the CLI implementation.

Flow:

1. Extension uses native messaging host to read AWS credentials (from ~/.aws/credentials or environment)
2. User enables Bedrock mode in settings and specifies region/profile
3. Extension connects via AWS Bedrock
4. Functions identically to standard version with different auth backend

Note: Would require native messaging component since Chrome extensions can't directly access filesystem - similar to how extensions like 1Password work.

Important: Must honor AWS Bedrock's data privacy guarantees - no data should leak to Anthropic's services. Organizations choose Bedrock specifically for data isolation.

Alternative Solutions

Current workaround: CLI only - extension cannot be used.

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example

_No response_

Additional Context

Additional Context:

• CLI has full Bedrock support via environment variables
• Enterprises use Bedrock for centralized access with corporate security