anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 10:15:31 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

fix(provider): Enable credential_process and default profile support for Amazon Bedrock #5957

New Issue
Open
opened 2026-02-16 17:58:47 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 17:58:47 -05:00
Owner
Copy Link
Copy Source

Originally created by @luqs1 on GitHub (Jan 14, 2026).

Originally assigned to: @thdxr on GitHub.

Description

Amazon Bedrock provider doesn't support credential_process in ~/.aws/config or the default AWS profile when AWS_PROFILE is not explicitly set.

Current Behavior

When using credential_process in ~/.aws/config:

[default]
credential_process = aws-vault exec default --json

Running opencode without setting AWS_PROFILE results in the Bedrock provider not loading. The /models command doesn't show Bedrock models.

Expected Behavior

OpenCode should support all AWS credential sources that the AWS SDK supports, including:

  • credential_process in ~/.aws/config
  • Default profile when AWS_PROFILE is not set
  • All other credential sources that fromNodeProviderChain() discovers

Root Cause

Line 202 in packages/opencode/src/provider/provider.ts has a guard clause that returns early if no explicit credentials are detected:

if (!profile && !awsAccessKeyId && !awsBearerToken && !awsWebIdentityTokenFile) 
  return { autoload: false }

This prevents fromNodeProviderChain() from running, which would otherwise discover credential_process and default profile credentials.

Environment

  • OpenCode version: 1.1.20
  • Platform: macOS/Linux
  • AWS credential method: credential_process in ~/.aws/config

Reproduction

  1. Set up ~/.aws/config with credential_process: 
    [default]
credential_process = aws-vault exec default --json
  2. Run opencode (without setting AWS_PROFILE)
  3. Run /models command
  4. Observe: Bedrock models are not listed

Related

  • Similar to PR #8461 which added AWS_WEB_IDENTITY_TOKEN_FILE support
  • The code already imports fromNodeProviderChain() which supports credential_process
  • This affects users of aws-vault, saml2aws, granted, and other credential helpers
Originally created by @luqs1 on GitHub (Jan 14, 2026). Originally assigned to: @thdxr on GitHub. ## Description Amazon Bedrock provider doesn't support `credential_process` in `~/.aws/config` or the default AWS profile when `AWS_PROFILE` is not explicitly set. ## Current Behavior When using `credential_process` in `~/.aws/config`: ```ini [default] credential_process = aws-vault exec default --json ``` Running `opencode` without setting `AWS_PROFILE` results in the Bedrock provider not loading. The `/models` command doesn't show Bedrock models. ## Expected Behavior OpenCode should support all AWS credential sources that the AWS SDK supports, including: - `credential_process` in `~/.aws/config` - Default profile when `AWS_PROFILE` is not set - All other credential sources that `fromNodeProviderChain()` discovers ## Root Cause Line 202 in `packages/opencode/src/provider/provider.ts` has a guard clause that returns early if no explicit credentials are detected: ```typescript if (!profile && !awsAccessKeyId && !awsBearerToken && !awsWebIdentityTokenFile) return { autoload: false } ``` This prevents `fromNodeProviderChain()` from running, which would otherwise discover `credential_process` and default profile credentials. ## Environment - OpenCode version: 1.1.20 - Platform: macOS/Linux - AWS credential method: credential_process in ~/.aws/config ## Reproduction 1. Set up `~/.aws/config` with credential_process: ```ini [default] credential_process = aws-vault exec default --json ``` 2. Run `opencode` (without setting AWS_PROFILE) 3. Run `/models` command 4. Observe: Bedrock models are not listed ## Related - Similar to PR #8461 which added `AWS_WEB_IDENTITY_TOKEN_FILE` support - The code already imports `fromNodeProviderChain()` which supports credential_process - This affects users of aws-vault, saml2aws, granted, and other credential helpers
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#5957
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?